Open danielmarbach opened 1 year ago
Thank you for your feedback. Tagging and routing to the team member best able to assist.
Thanks for filing this @danielmarbach. You are correct that we would need some sort of service support to add validation here as we try to avoid hard-coding limits on the client. I think you have linked the correct issue - https://github.com/Azure/azure-sdk-for-net/issues/21451, as the setting for the max messages in a transaction could be included as part of the same set of Link Settings as the setting for overall max messages. I am going to mark this issue as Service Attention and also add a comment to the linked issue.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @shankarsama @DorothySun216 @EldertGrootenboer @saglodha.
We have assigned an engineer to look further into this issue. We will update this issue when we have more information.
Thank you for your feedback. We have brought this item in our current planning, and should be able to provide an update in the coming months.
Library name
Azure.Messaging.ServiceBus
Please describe the feature.
Related https://github.com/Azure/azure-sdk-for-net/issues/21451 and https://github.com/Azure/azure-sdk-for-net/pull/19125
Currently, when transactions across entities are used, the
TryAdd
method does allow adding more items to the batch than the service can handle.The current service restriction is 100 items per transaction.
I realize this might be very tricky to improve, and potentially not even possible without actually calling the service and the service returning the maximum number of items per transaction. I also haven't done any investigations if it is even possible to discover on the client-side the number of transaction enlistments from potentially multiple batches.
Yet, I want to raise this as a discussion item to explore if there is anything that could be done, similar to whether it is possible to improve the maximum number of items that can ever be sent within a batch depending on the tier.