The current azure-servicebus library has this SendVia option that one can set on the sender in order to use the transactions across entities. As seen in #16942, we are moving to an implicit transactional via sender model where the user does not have to provide the SendVia option anymore.
This issue is to remove this option from the newer azure-messaging-servicebus library so that in a future update, we can add the implicit transactional via sender model without needing to deprecate the SendVia option.
Please note, in the newer azure-messaging-servicebus library, this option was split to viaQueueName and viaTopicName
This issue is to track
- removal of viaQueueName and viaTopicName from the sender sub builder
- removal of viaQueueName and viaTopicName properties on the sender client
cc @hemanttanwar, @conniey, @YijunXieMS
The current azure-servicebus library has this SendVia option that one can set on the sender in order to use the transactions across entities. As seen in #16942, we are moving to an implicit transactional via sender model where the user does not have to provide the SendVia option anymore.
This issue is to remove this option from the newer azure-messaging-servicebus library so that in a future update, we can add the implicit transactional via sender model without needing to deprecate the SendVia option.
Please note, in the newer azure-messaging-servicebus library, this option was split to viaQueueName and viaTopicName
This issue is to track
cc @hemanttanwar, @conniey, @YijunXieMS