-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Service Bus] ATOM API: CreateTopicOptions missing field - FilteringMessagesBeforePublishing #14718
Comments
@axisc, We see this property in the older WindowsAzure.ServiceBus package, but not in the later Microsoft.Azure.ServiceBus package. See Can you share if this property is still valid and is worth carrying over to the new libraries for Service Bus? |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jfggdl, @axisc. Issue DetailsFilteringMessagesBeforePublishing is present in .NET but not in JS.
|
Removing milestone pending verification from @axisc that it needs to exist in our track 2 SDKs. |
I don't see this exposed in the public APIs of the Azure.Messaging.ServiceBus package though... Same goes for the TopicDescription in the older .NET package Microsoft.Azure.ServiceBus It only exists in the even older WindowsAzure.ServiceBus where it was meant to be used only in dev for testing purposes. See TopicDescription.EnableFilteringMessagesBeforePublishing It is fair to say that we do not plan to carry this forward. @JoshLove-msft You can remove the dead code in https://github.com/Azure/azure-sdk-for-net/blob/8af2dfc32c96ef3e340f9d20013bf588d97ea756/sdk/servicebus/Azure.Messaging.ServiceBus/src/Administration/TopicPropertiesExtensions.cs#L175 |
FilteringMessagesBeforePublishing is present in .NET but not in JS.
Noticed by @richardpark-msft at #14692
Reference - https://github.com/Azure/azure-sdk-for-net/blob/8af2dfc32c96ef3e340f9d20013bf588d97ea756/sdk/servicebus/Azure.Messaging.ServiceBus/src/Administration/TopicPropertiesExtensions.cs#L175
The text was updated successfully, but these errors were encountered: