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.

Sign up for GitHub

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

Jump to bottom

[FEATURE REQ] Expose RequestContext overloads on BlobBaseClient methods to support non-throwing reads #48607

Open
ReubenBond opened this issue Mar 6, 2025 · 1 comment
Open

[FEATURE REQ] Expose RequestContext overloads on BlobBaseClient methods to support non-throwing reads #48607

ReubenBond opened this issue Mar 6, 2025 · 1 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. 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

@ReubenBond
Copy link
Contributor

Library name

Azure.Storage.Blobs

Please describe the feature.

It's common to perform speculative point-reads against blobs which may not exist. In these cases, a 404 response is expected and not an error. Exceptions thrown in these cases are undesirable: they incur a substantial performance cost and they show up in logs/traces as failures.

Exposing overloads on BlobBaseClient methods which accept a RequestContext parameter would allow callers to configure the operation to not throw when a blob is not found by setting RequestContext.ErrorOptions to ErrorOptions.NoThrow, and to not log an error by adding a classifier

Alternatively, *IfExists APIs could be added for the specific scenario.

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

github-actions bot commented Mar 6, 2025

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @amnguye @jalauzon-msft @jaschrep-msft @nickliu-msft @seanmcc-msft.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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. 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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ReubenBond @jsquire