Azure / Azure/azure-storage-python

uploaded files sometimes get truncated

Abierto
#632 1 comentario 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
343
Forks
243
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### 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.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza en BlockBlobService().create_blob_from_path y reproduce la carga con los dos casos de archivos JSON descritos en el issue, comparando el contenido local y el cargado. Se considera terminado cuando se haya identificado por qué algunas cargas quedan truncadas y se haya confirmado que los archivos afectados se cargan íntegramente; el issue no proporciona ningún test ni archivo fuente específicos.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
azure, python
Área
backend, cloud
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.