Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QUERY] Azure.Storage.DataMovement doesn't checkpoint individual blob transfer progress #47719

Open
aloncatz opened this issue Jan 6, 2025 · 2 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)

Comments

@aloncatz
Copy link

aloncatz commented Jan 6, 2025

Library name and version

Azure.Storage.DataMovement.Blobs 12.0.0-beta.6

Query/Question

I'm trying to use Azure.Storage.DataMovement to upload big files from a user's computer to Azure Blob Storage. Looks like the library doesn't checkpoint upload progress of a single big file. Does it mean that checkpointing only applies to uploading of multiple files, i.e. it will track which file has not been uploaded successfully, and re-upload it fully?

Environment

No response

@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files) labels Jan 6, 2025
Copy link

github-actions bot commented Jan 6, 2025

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @xgithubtriage.

@amnguye amnguye added feature-request This issue requires a new behavior in the product in order be resolved. and removed needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team labels Feb 4, 2025
@amnguye amnguye self-assigned this Feb 4, 2025
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Feb 4, 2025
@amnguye
Copy link
Member

amnguye commented Feb 4, 2025

Hi,

We currently do not support checkpointing in the middle of a large single file/blob. We only support checkpointing per file.

Which the transfer to your question, yes checkpointing currently only applies to uploading multiple files and track which ones haven't been transferred yet and which ones has.

I've relabeled your issue as a feature request as it sounds like you're asking for checkpointing to be enhanced.

@amnguye amnguye removed the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Feb 4, 2025
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

2 participants