Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit c0aef01

Browse files
committedSep 23, 2020
add images for example
1 parent f61b228 commit c0aef01

File tree

9 files changed

+52
-4
lines changed

9 files changed

+52
-4
lines changed
 

‎articles/stream-analytics/event-hubs-output.md

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: mamccrea
66
ms.reviewer: mamccrea
77
ms.service: stream-analytics
88
ms.topic: conceptual
9-
ms.date: 08/25/2020
9+
ms.date: 09/23/2020
1010
---
1111
# Event Hubs output from Azure Stream Analytics
1212

@@ -40,7 +40,23 @@ The maximum message size is 256 KB or 1 MB per message. For more information, se
4040

4141
## Custom metadata properties for output
4242

43-
You can attach query columns as user properties to your outgoing messages. These columns don't go into the payload. The properties are present in the form of a dictionary on the output message. *Key* is the column name and *value* is the column value in the properties dictionary. All Stream Analytics data types are supported except Record and Array.
43+
You can attach query columns as user properties to your outgoing messages. These columns don't go into the payload. The properties are present in the form of a dictionary on the output message. *Key* is the column name and *value* is the column value in the properties dictionary. All Stream Analytics data types are supported except Record and Array.
44+
45+
In the following example, the fields `DeviceId` and `DeviceStatus` are added to the metadata.
46+
47+
1. Use the following query:
48+
49+
```sql
50+
select *, DeviceId, DeviceStatus from iotHubInput
51+
```
52+
53+
1. Configure `DeviceId,DeviceStatus` as property columns in the output.
54+
55+
:::image type="content" source="media/event-hubs-output/property-columns.png" alt-text="Property columns":::
56+
57+
The following image is of the expected output message properties inspected in EventHub using [Service Bus Explorer](https://github.com/paolosalvatori/ServiceBusExplorer).
58+
59+
:::image type="content" source="media/event-hubs-output/custom-properties.png" alt-text="Event custom properties":::
4460

4561
## Next steps
4662

Loading
Loading
Loading
Loading
Loading
Loading

‎articles/stream-analytics/service-bus-queues-output.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: mamccrea
66
ms.reviewer: mamccrea
77
ms.service: stream-analytics
88
ms.topic: conceptual
9-
ms.date: 08/25/2020
9+
ms.date: 09/23/2020
1010
---
1111

1212
# Service Bus queues output from Azure Stream Analytics
@@ -47,6 +47,22 @@ The maximum message size is 256 KB per message for Standard tier and 1MB for Pre
4747

4848
You can attach query columns as user properties to your outgoing messages. These columns don't go into the payload. The properties are present in the form of a dictionary on the output message. *Key* is the column name and *value* is the column value in the properties dictionary. All Stream Analytics data types are supported except Record and Array.
4949

50+
In the following example, the fields `DeviceId` and `DeviceStatus` are added to the metadata.
51+
52+
1. Use the following query:
53+
54+
```sql
55+
select *, DeviceId, DeviceStatus from iotHubInput
56+
```
57+
58+
1. Configure `DeviceId,DeviceStatus` as property columns in the output.
59+
60+
:::image type="content" source="media/service-bus-queues-output/property-columns.png" alt-text="Property columns":::
61+
62+
The following image is of the expected output message properties inspected in EventHub using [Service Bus Explorer](https://github.com/paolosalvatori/ServiceBusExplorer).
63+
64+
:::image type="content" source="media/service-bus-queues-output/custom-properties.png" alt-text="Event custom properties":::
65+
5066
## System properties
5167

5268
You can attach query columns as [system properties](https://docs.microsoft.com/dotnet/api/microsoft.servicebus.messaging.brokeredmessage?view=azure-dotnet#properties&preserve-view=true) to your outgoing service bus Queue or Topic messages.

‎articles/stream-analytics/service-bus-topics-output.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: mamccrea
66
ms.reviewer: mamccrea
77
ms.service: stream-analytics
88
ms.topic: conceptual
9-
ms.date: 08/25/2020
9+
ms.date: 09/23/2020
1010
---
1111

1212
# Service Bus Topics output from Azure Stream Analytics
@@ -42,6 +42,22 @@ The maximum message size is 256 KB per message for Standard tier and 1MB for Pre
4242

4343
You can attach query columns as user properties to your outgoing messages. These columns don't go into the payload. The properties are present in the form of a dictionary on the output message. *Key* is the column name and *value* is the column value in the properties dictionary. All Stream Analytics data types are supported except Record and Array.
4444

45+
In the following example, the fields `DeviceId` and `DeviceStatus` are added to the metadata.
46+
47+
1. Use the following query:
48+
49+
```sql
50+
select *, DeviceId, DeviceStatus from iotHubInput
51+
```
52+
53+
1. Configure `DeviceId,DeviceStatus` as property columns in the output.
54+
55+
:::image type="content" source="media/service-bus-topics-output/property-columns.png" alt-text="Property columns":::
56+
57+
The following image is of the expected output message properties inspected in EventHub using [Service Bus Explorer](https://github.com/paolosalvatori/ServiceBusExplorer).
58+
59+
:::image type="content" source="media/service-bus-topics-output/custom-properties.png" alt-text="Event custom properties":::
60+
4561
## System properties
4662

4763
You can attach query columns as [system properties](https://docs.microsoft.com/dotnet/api/microsoft.servicebus.messaging.brokeredmessage?view=azure-dotnet#properties&preserve-view=true) to your outgoing service bus Queue or Topic messages.

0 commit comments

Comments
 (0)
Please sign in to comment.