Skip to content

Commit 7b6cf45

Browse files
committed
fix heads and spelling
1 parent a675f4d commit 7b6cf45

File tree

1 file changed

+6
-6
lines changed
  • docs/integrations/data-ingestion/clickpipes

1 file changed

+6
-6
lines changed

docs/integrations/data-ingestion/clickpipes/kafka.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -81,32 +81,32 @@ Clicking on "Create ClickPipe" will create and run your ClickPipe. It will now b
8181
## Schema registries {#schema-registries}
8282
ClickPipes supports schema registries for Avro data streams.
8383

84-
### Supported registries
85-
Schema registries that use the Confluent Schema Registry API are suppoirted. This includes:
84+
### Supported registries {#supported-schema-registries}
85+
Schema registries that use the Confluent Schema Registry API are supported. This includes:
8686
- Confluent Kafka and Cloud
8787
- Redpanda
8888
- AWS MSK
8989
- Upstash
9090

9191
ClickPipes is not currently compatible with the AWS Glue Schema registry or the Azure Schema Registry.
9292

93-
### Configuration
93+
### Configuration {#schema-registry-configuration}
9494

9595
A schema registry can be configured by when setting up a ClickPipe. This can be configured in one of three ways:
96-
96+
9797
1. Providing the root schema registry URL (e.g. `https://registry.example.com`). **This is the preferred method.**
9898
2. Providing a complete path to the schema id (e.g. `https://registry.example.com/schemas/ids/1000`)
9999
3. Providing a complete path to the schema subject (e.g. `https://registry.example.com/subjects/events`)
100100
- Optionally, a specific version can be referenced by appending `/versions/[version]` to the url (otherwise ClickPipes will retrieve the latest version).
101101

102-
### How it works
102+
### How it works {#how-schema-registries-work}
103103
ClickPipes dynamically retrieves and applies the Avro schema from the configured Schema Registry.
104104
- If there's a schema id embedded in the message, it will use that to retrieve the schema.
105105
- If there's no schema id embedded in the message, it will use the schema id or subject name specified in the ClickPipe configuration to retrieve the schema.
106106
- If the message is written without an embedded schema id, and no schema id or subject name is specified in the ClickPipe configuration, then the schema will not be retrieved and the message will be skipped with a `SOURCE_SCHEMA_ERROR` logged in the ClickPipes errors table.
107107
- If the message does not conform to the schema, then the message will be skipped with a `DATA_PARSING_ERROR` logged in the ClickPipes errors table.
108108

109-
### Schema mapping
109+
### Schema mapping {#schema-mapping}
110110
The following rules are applied to the mapping between the retrieved Avro schema and the ClickHouse destination table:
111111

112112
- If the Avro schema contains a field that is not included in the ClickHouse destination mapping, that field is ignored.

0 commit comments

Comments
 (0)