Skip to content

Commit 7052471

Browse files
author
ClareMSYanGit
committed
Fixed invalid link
1 parent a5e84a7 commit 7052471

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/iot-hub/iot-hub-query-avro-data.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.author: Kevin.Saye
1616

1717
This article is about how to query Avro data for efficiently routing messages from Azure IoT Hub to Azure services. Following the blog post announcement—[Azure IoT Hub message routing: now with routing on message body], IoT Hub supports routing on either properties or the message body. See also [Routing on message bodies][Routing on message bodies].
1818

19-
The challenge has been that when Azure IoT Hub routes messages to blob storage, IoT Hub writes the content in Avro format, which has both message body and message properties. Note that IoT Hub only supports writing data to blob storage in the Avro data format, and this format is not used for any other endpoints. See [When using Azure Storage containers][Using Azure storage containers]. While the Avro format is great for data/message preservation, it's challenging for querying the data. In comparison, JSON or CSV format is much easier for querying data.
19+
The challenge has been that when Azure IoT Hub routes messages to blob storage, IoT Hub writes the content in Avro format, which has both message body and message properties. Note that IoT Hub only supports writing data to blob storage in the Avro data format, and this format is not used for any other endpoints. See [When using Azure Storage containers][When using Azure storage containers]. While the Avro format is great for data/message preservation, it's challenging for querying the data. In comparison, JSON or CSV format is much easier for querying data.
2020

2121
To solve this, you can use many of the big data patterns for both transforming and scaling data to address non-relational big data needs and formats. One of the patterns, a “pay per query” pattern, is Azure Data Lake Analytics (ADLA). It is the focus of this article. Though you could easily execute the query in Hadoop or other solutions, ADLA is often better suited for this “pay per query” approach. There is an “extractor” for Avro in U-SQL. See [U-SQL Avro Example].
2222

@@ -180,7 +180,7 @@ To learn more about message routing in IoT Hub, see [Send and receive messages w
180180
[Azure IoT Hub message routing: now with routing on message body]: https://azure.microsoft.com/blog/iot-hub-message-routing-now-with-routing-on-message-body/
181181

182182
[Routing on message bodies]: iot-hub-devguide-query-language.md#routing-on-message-bodies
183-
[Using Azure storage containers]:iot-hub-devguide-endpoints#when-using-azure-storage-containers
183+
[When using Azure storage containers]:iot-hub-devguide-endpoints.md#when-using-azure-storage-containers
184184

185185
[U-SQL Avro Example]:https://github.com/Azure/usql/tree/master/Examples/AvroExamples
186186

0 commit comments

Comments
 (0)