Skip to content

Commit a0a90e9

Browse files
committed
Revert doc & rebase
1 parent 729df9d commit a0a90e9

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

README.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,8 @@ Kafkactl enables the deployment of Kafka resources to Ns4Kafka using YAML descri
5858
* [Connect Cluster](#connect-cluster-2)
5959
* [Kafka Streams](#kafka-streams)
6060
* [Schema](#schema-2)
61+
* [Local file](#local-file)
62+
* [Inline](#inline)
6163
* [Administrator](#administrator)
6264
* [Namespace](#namespace)
6365
* [Validation Constraints](#validation-constraints)
@@ -904,6 +906,8 @@ metadata:
904906
The `Schema` resource allows you to declare subjects for your schemas. You can either reference a local `avsc` file
905907
with `spec.schemaFile`, or define your schema directly inline with `spec.schema`.
906908

909+
- `metadata.name` must be the subject name in the Schema Registry. It must follow the naming strategy allowed at the namespace level, which can be one of `TopicNameStrategy`, `RecordNameStrategy`, or `TopicRecordNameStrategy`.
910+
907911
##### Local file
908912

909913
```yml
@@ -1161,6 +1165,19 @@ connectValidator:
11611165
- io.confluent.connect.jdbc.JdbcSourceConnector
11621166
```
11631167

1168+
##### Subject Naming Strategy
1169+
1170+
The authorized subject naming strategy can be enforced at the namespace level.
1171+
1172+
For Confluent Cloud clusters, if not specified, the strategy defaults to `TopicNameStrategy`. It can be configured in the `topicValidator` using the
1173+
[`confluent.key.subject.name.strategy`](https://docs.confluent.io/platform/current/installation/configuration/topic-configs.html#confluent-key-subject-name-strategy)
1174+
or [`confluent.value.subject.name.strategy`](https://docs.confluent.io/platform/current/installation/configuration/topic-configs.html#confluent-value-subject-name-strategy) properties, with one of the following values:
1175+
- `TopicNameStrategy`: `<topic>-key` or `<topic>-value`
1176+
- `RecordNameStrategy`: `<full_record_name>`
1177+
- `TopicRecordNameStrategy`: `<topic>-<full_record_name>`
1178+
1179+
For self-managed clusters, the strategy defaults to `TopicNameStrategy` and cannot be changed.
1180+
11641181
#### ACL Owner
11651182

11661183
ACLs with owner permission can only be deployed by administrators.

0 commit comments

Comments
 (0)