[Service Bus] Remove send via option from sender builder - #17018
Conversation
|
/azp run java - servicebus - ci |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| } | ||
| } | ||
| // @Test | ||
| // void viaQueueMessageSendTest() { |
There was a problem hiding this comment.
Should we remove them instead of comment out?
There was a problem hiding this comment.
I kept them so that we can use them in the next update when we add the transaction feature for cross entities back in
There was a problem hiding this comment.
I can delete the entire file if we feel otherwise.
There was a problem hiding this comment.
Normally we delete the test if we do not need it soon. We can always get it back from git history and old commits.
If we are going to introduce this next months or soon, we can disable by adding @Disable annotation.
@Disabled("Reason why disable.")
There are other test in this file, so we can not delete the file but remove the test.
|
Anyone know why the tests are failing only on Mac? |
My new unit test that tests timeout. I'll help you retry the run to pass it. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| } | ||
| } | ||
| // @Test | ||
| // void viaQueueMessageSendTest() { |
There was a problem hiding this comment.
Normally we delete the test if we do not need it soon. We can always get it back from git history and old commits.
If we are going to introduce this next months or soon, we can disable by adding @Disable annotation.
@Disabled("Reason why disable.")
There are other test in this file, so we can not delete the file but remove the test.
I have not touched MAC in last 1 year. |
|
What about ViaPartitionKey? Should that be removed also? |
|
@JoshLove-msft Based on the discussions on the new design for cross entity transactions, it didnt look like anything was going to change with the |
As described in #17017, we want to remove the send via options from the public API surface so that in a future updated we can provide a cleaner solution from transaction across entities.
In this PR I have,
viaQueueNameandviaTopicNamefrom the sender builderCloses #17017