locked
MessageId when sending to Service Bus Queue RRS feed

  • Question

  • I have a stream analytics job connected to a Service Bus Queue as output and an IoTHub as input.

    Service Bus Queue has a Message Id field that I use for duplicate detection purposes.

    Stream Analytics sets this value automatically if I understood it correctly but what is the logic behind?

    If I send messages manually to a service bus queue it is beeing set automatically to a GUID like format (55a9cf08-9c35-4ffb-a197-539e5e5406a1). But messages from stream analytics job get message ids of another format (8103bab7374f4ed2bb67c329ab471180). Although both are 32 characters long I just wonder what kind of logic is used to generate those message ids from stream analytics.

    Is it just an automatic GUID generation?

    Tuesday, April 4, 2017 7:18 AM

All replies

  • Yes currently it is simply a unique guid. The formats look different but you can parse them in anyway you like based on the Guid Format.

    [Disclaimer] This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all.

    Tuesday, April 4, 2017 6:37 PM