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

[FEATURE REQ][Storage] Ability to receive ONE message from Queue #14211

Closed
kasobol-msft opened this issue Aug 13, 2020 · 5 comments
Closed

[FEATURE REQ][Storage] Ability to receive ONE message from Queue #14211

kasobol-msft opened this issue Aug 13, 2020 · 5 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 Service Attention Workflow: This issue is responsible by Azure service team. Storage Storage Service (Queues, Blobs, Files)
Milestone

Comments

@kasobol-msft
Copy link
Contributor

kasobol-msft commented Aug 13, 2020

Library or service name.
Azure.Storage.Queues

Is your feature request related to a problem? Please describe.

I'm working with codebase written against V11 storage SDK, migrating to V12. There's a lot of code that tries to peek or receive just one message from the queue. The APIs available on QueueClient make this task kind of cumbersome, i.e. a lot of :
(await _queue.ReceiveMessagesAsync(1)).Value.FirstOrDefault();

Can we add APIs like queue.ReceiveMessageAsync() ?? And similar for Peek ?

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 13, 2020
@kasobol-msft kasobol-msft added the Storage Storage Service (Queues, Blobs, Files) label Aug 13, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Aug 13, 2020
@kasobol-msft kasobol-msft added Client This issue points to a problem in the data-plane of the library. Service Attention Workflow: This issue is responsible by Azure service team. labels Aug 13, 2020
@ghost
Copy link

ghost commented Aug 13, 2020

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

@kasobol-msft
Copy link
Contributor Author

@tg-msft Do you think it's a reasonable ask?

@kasobol-msft kasobol-msft added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Aug 13, 2020
@ghost ghost added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Aug 13, 2020
@tg-msft
Copy link
Member

tg-msft commented Aug 13, 2020

I think that makes a lot of sense. We originally didn't for the sake of simplicity, but I've seen more and more folks having a bad time with this. Let's just make sure we're aligned with what ServiceBus is doing too. @JoshLove-msft - is SB adding an overload to return single messages?

@JoshLove-msft
Copy link
Member

JoshLove-msft commented Aug 13, 2020

I think that makes a lot of sense. We originally didn't for the sake of simplicity, but I've seen more and more folks having a bad time with this. Let's just make sure we're aligned with what ServiceBus is doing too. @JoshLove-msft - is SB adding an overload to return single messages?

Yes, SB has methods to receive a single message, a list of messages (specifying maxCount), or an IAsyncEnumerable of messages.

@amnguye amnguye added customer-reported Issues that are reported by GitHub users external to the Azure organization. and removed customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Aug 13, 2020
@tg-msft
Copy link
Member

tg-msft commented Aug 14, 2020

And it looks like ServiceBus is also calling it ReceiveMessage and ReceiveMessages per https://apiview.dev/Assemblies/Review/b5d7e3304000449c859c2016f718db52#Azure.Messaging.ServiceBus.ServiceBusReceiver.

This plan sounds good to me.

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

5 participants