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

[Storage] Implement retriable data streamer #5121

Closed
annatisch opened this issue May 6, 2019 · 2 comments
Closed

[Storage] Implement retriable data streamer #5121

annatisch opened this issue May 6, 2019 · 2 comments
Assignees
Labels
blocking-release Blocks release Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files)

Comments

@annatisch
Copy link
Member

  • See .Net and Go implementations
@annatisch annatisch added Storage Storage Service (Queues, Blobs, Files) Client This issue points to a problem in the data-plane of the library. labels May 6, 2019
@rakshith91 rakshith91 self-assigned this Sep 26, 2019
@mayurid
Copy link
Member

mayurid commented Oct 9, 2019

#7504
@rakshith91 : Please look at this in reference with the above issue.

@mayurid mayurid added the blocking-release Blocks release label Oct 9, 2019
@mayurid mayurid assigned annatisch and unassigned rakshith91 Oct 15, 2019
@annatisch
Copy link
Member Author

I've confirmed that all streamed requests/responses are going through the pipeline retry policy and raised errors handled accordingly.
If a particular chunk fails after max retries, the upload/download will fail.
Each chunk in the upload/download will be subject to the retry policy individually.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
blocking-release Blocks release Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

3 participants