Thank you for all the votes and feedback. We have started work on this and the capability will be supported soon. If you would like to get in touch with us to discuss your scenarios, please fill this form: https://aka.ms/ApplicationGatewayCohortAvi Mualem commented
whats the ETA for this feature?
i find it essential for any fine grained API gateway product.
in addition the exact same functionality is implemented in the Azure API management so i honestly cant understand why it shouldn't be available in the API gateway.
Rest assured we still have this request in mind and are continually reviewing it. Please keep your feedback coming!
Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.
The newly released .NET SDK v3 now includes support for x-partition queries using Offset/Limit. You can learn more about v3 SDK and try it and provide feedback on our github repo here.
We will also be back-porting this functionality to our .NET v2 SDK. This work will begin shortly and we anticipate it to be released in September.
Once that is released we will mark this feature as complete.
Thank you for your patience and votes.
363 votesAvi Mualem commented
I truly believe this feature is essential to any message brokering platform.
In modern distributed systems which based upon eventual consistency paradigm various business scenarios use topics with multiple subscriptions often need to assure that each subscription logic will be invoked eventually.
i'm aware to the fact that the dead letter subscriber can send a message to the original topic with a custom filter that will make sure only dedicated subscriber will get invoked but this workaround doesn't feel like an actual solution for the issue.