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

GetEntityOrNullAsync #27419

Closed
fabiomaulo opened this issue Mar 8, 2022 · 3 comments
Closed

GetEntityOrNullAsync #27419

fabiomaulo opened this issue Mar 8, 2022 · 3 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. 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 Tables

Comments

@fabiomaulo
Copy link

fabiomaulo commented Mar 8, 2022

Library name

Azure.Data.Tables

Descrption

The matter that we have an Azure.RequestFailedException in front of an unexistent entity sounds like a regression to the dawn of Azure SDK.
You already have a 404 but, when I'm trying to read the value you throw me an exception with the status-code 404.
My use-case has some write-once properties so I can´t use Upsert with the merge.
A GetEntityOrNull, and its pair GetEntityOrNullAsync, would be very useful to avoid the noise of try-catch and the performance issue of throwing the exception (and its call-stack).
Thanks

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Mar 8, 2022
@fabiomaulo
Copy link
Author

An alternative could be an extension method as TryGetEntity with the behavior similar to the IDictionary<T>.TryGetValue

@jsquire jsquire added 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 Tables labels Mar 8, 2022
@jsquire
Copy link
Member

jsquire commented Mar 8, 2022

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 8, 2022
@christothes
Copy link
Member

Duplicate of #25626

@christothes christothes marked this as a duplicate of #25626 Mar 8, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Mar 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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 Tables
Projects
None yet
Development

No branches or pull requests

3 participants