Azure / Azure/azure-storage-python
uploaded files sometimes get truncated
- Vorherrschende Sprache
- Python
- Sterne
- 343
- Forks
- 243
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### 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.
Beitragsleitfaden
Rechercherichtung
Beginne bei BlockBlobService().create_blob_from_path und reproduziere den Upload mit den beiden im Issue beschriebenen JSON-Dateifällen, wobei du die lokalen und hochgeladenen Inhalte vergleichst. Erledigt ist die Aufgabe, wenn festgestellt wurde, warum einige Uploads abgeschnitten werden, und bestätigt wurde, dass die betroffenen Dateien vollständig hochgeladen werden; das Issue nennt weder einen bestimmten Test noch eine Quelldatei.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- azure, python
- Bereich
- backend, cloud
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100