Skip to content

Commit 3638738

Browse files
committed
contd
1 parent 99db8a5 commit 3638738

File tree

1 file changed

+10
-3
lines changed

1 file changed

+10
-3
lines changed

articles/iot-operations/connect-to-cloud/concept-schema-registry.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how schema registry handles message schemas to work with Azur
44
author: kgremban
55
ms.author: kgremban
66
ms.topic: conceptual
7-
ms.date: 10/30/2024
7+
ms.date: 11/14/2024
88

99
#CustomerIntent: As an operator, I want to understand how I can use message schemas to filter and transform messages.
1010
---
@@ -106,13 +106,13 @@ Output schemas are associated with dataflow destinations.
106106
In the operations experience portal, you can configure output schemas for the following destination endpoints that support Parquet output:
107107

108108
* local storage
109-
* Fabric
109+
* Fabric OneLake
110110
* Azure Storage (ADLS Gen2)
111111
* Azure Data Explorer
112112

113113
Note: The Delta schema format is used for both Parquet and Delta output.
114114

115-
If you use Bicep or Kubernetes, you can configure output schemas using JSON output for MQTT and Kafka destination endpoints. MQTT and Kafka destinations don't support Delta format.
115+
If you use Bicep or Kubernetes, you can configure output schemas using JSON output for MQTT and Kafka destination endpoints. MQTT- and Kafka-based destinations don't support Delta format.
116116

117117
For these dataflows, the operations experience applies any transformations to the input schema then creates a new schema in Delta format. When the dataflow custom resource (CR) is created, it includes a `schemaRef` value that points to the generated schema stored in the schema registry.
118118

@@ -140,6 +140,13 @@ The following example creates a schema called `myschema` from inline content and
140140
az iot ops schema create -n myschema -g myresourcegroup --registry myregistry --format delta --type message --version-content '{\"hello\": \"world\"}' --ver 14
141141
```
142142

143+
>[!TIP]
144+
>If you don't know your registry name, use the `schema registry list` command to query for it. For example:
145+
>
146+
>```azurecli
147+
>az iot ops schema registry list -g myresourcegroup --query "[].{Name:name}" -o tsv
148+
>```
149+
143150
Once the `create` command is completed, you should see a blob in your storage account container with the schema content. The name for the blob is in the format `schema-namespace/schema/version`.
144151
145152
You can see more options with the helper command `az iot ops schema -h`.

0 commit comments

Comments
 (0)