You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `Schema` resource allows you to declare subjects for your schemas. You can either reference a local `avsc` file
905
907
with `spec.schemaFile`, or define your schema directly inline with `spec.schema`.
906
908
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
+
907
911
##### Local file
908
912
909
913
```yml
@@ -1161,6 +1165,19 @@ connectValidator:
1161
1165
- io.confluent.connect.jdbc.JdbcSourceConnector
1162
1166
```
1163
1167
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
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:
0 commit comments