1

I'm using Azure Service Bus Explorer in managing subscriptions for existing Azure Service Bus topics. Now we have a new Topic that will receive messages from multiple source systems. Based on the source system i need to create different subscriptions. Below are the sample messages that we recieve

Message1:

{
  "entity": {
    "id": "20190501",
    "source": "system1",
    "body": "{\r\n  \"Addressid\": \"74C9\",\r\n  \"Start\": \"2016-07-17T21:06:10.983\",\r\n  \"OrgID\": \"7204055\",\r\n  \"Email\": \"test@gmail.com\",\r\n  \"DeptID\": 998\r\n}",
    "createDate": "2019-05-16T12:47:52.4658011Z",
    "isDeleted": false
  },
  "operation": "POST"
}

Message2:

{
  "entity": {
    "id": "20190501",
    "source": "system2",
    "body": "{\r\n  \"AC_ID\": \"74C9\",\r\n  \"Name\": \"Name1\",\r\n  \"InventoryID\": \"4055\",\r\n  \"OtherID\": 998\r\n}",
    "createDate": "2019-05-16T12:47:52.4658011Z",
    "isDeleted": false
  },
  "operation": "POST"
}

I need to create two subscriptions with filter condition

Subscription1: with filter as "source": "system1"

Subscription2: with filter as "source": "system2"

Please help with me correct filter expression for the above service bus subscriptions that i need to create using service bus explorer.

user1941025
  • 541
  • 6
  • 21

1 Answers1

3

Azure Service Bus subscriptions operate on message headers/properties only. You can have either Boolean, Correlation, or SQL filters. SQLFilter class implements filtering that is beyond simple comparison and the syntax is a SQL-language based.

For example, "user.source='system1'" or "user.source in ('system1', 'system2')"

In your scenario, I'd use a correlation filter just because there's no need in SQL filter complexity. As well as you're interested in subscriptions, each with a distinct value used for filtering messages out. You'll find an example in this post.

Regardless if you use SQL of Correlation filter, filtering can only take place on the properties. You'll have to promote "source" value from the body of your message into one of the headers, system header or a custom header.

To see topics in action, there are a few official samples:

Sean Feldman
  • 23,443
  • 7
  • 55
  • 80
  • Thanks for your suggestion will try and make the change. – user1941025 May 22 '19 at 05:48
  • 1
    This will hopefully save someone else some time. If you have special characters in your user defined properties (ex: '-') use the following syntax in Azure Service Bus Explorer (or any place) to reference the property in a SQL filter: `user."X-Custom-Property"='ValueToCompare'` or `"X-Custom-Property"='ValueToCompare'` where 'X-Custom-Property' is your property name. – Lance Jul 03 '19 at 18:16