Description
Library name
Azure.Messaging.ServiceBus
Please describe the feature.
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.