Azure / Azure/azure-storage-python

uploaded files sometimes get truncated

Aperta
#632 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Python
Stelle
343
Fork
243
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

### Which service(blob, file, queue) does this issue concern?
Blob storage

### Which version of the SDK was used? Please provide the output of `pip freeze`.
azure-storage==0.34.3
azure-storage-blob==1.5.0
azure-storage-common==1.4.0
azure-storage-file==1.4.0
azure-storage-nspkg==3.0.0
azure-storage-queue==1.4.0

### What problem was encountered?
When uploading a json file with `BlockBlobService().create_blob_from_path`, sometimes the file gets truncated. This happens both when a file with the same name already exists in the blob storage and when it does not. It does not happen with all json files. I have one json file that contains the full dataset, for which upload does not give any issues. If I upload a json file with only a subset of the data, the file gets truncated. Both files were created in the same way.
Truncation happens during upload, the local version I have of the files are perfectly fine. Unfortunately I cannot share the files in question.
Uploading the file through the portal does not give any issues, so I suspect it has nothing to do with the file itself.
The issue is very similar to this one: https://github.com/Azure/azure-storage-azcopy/issues/207

### Have you found a mitigation/solution?
I manually upload the files through the portal, but this solution is not tenable.

Note: for table service, please post the issue here instead: https://github.com/Azure/azure-cosmosdb-python.

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Inizia da BlockBlobService().create_blob_from_path e riproduci l’upload con i due casi di file JSON descritti nell’issue, confrontando i contenuti locali e quelli caricati. Il lavoro è completato quando hai identificato perché alcuni upload vengono troncati e hai confermato che i file interessati vengono caricati integri; l’issue non indica alcun test o file sorgente specifico.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
azure, python
Ambito
backend, cloud
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.