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
Copy file name to clipboardExpand all lines: docs/kafka-schema-registry.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,7 @@ The `subject_name_strategy` determines how the stream looks up schemas in the re
42
42
43
43
| Strategy | Behavior | Derived Subject Name | Typical Use Case |
44
44
| :--- | :--- | :--- | :--- |
45
-
|**TopicNameStrategy**|**Default.** Assumes one schema per topic. |`<topic>-value`| Standard topics where every message follows the same structure. |
45
+
|**TopicNameStrategy**|**Default.** Assumes one schema per topic. |`<topic>-value`| Standard topics where every message follows the same structure. Note `schema_subject_name` will be ignored if configured. |
46
46
|**RecordNameStrategy**| Supports **mixed schemas** in one topic. |`schema_subject_name`| Consuming a specific record type from a stream containing multiple Avro types. `schema_subject_name` is usually full qualified record name like `com.x.y.z.RecordA`|
47
47
|**TopicRecordNameStrategy**| Scopes record names to a specific topic. |`<topic>-<schema_subject_name>`| Mixed topics where you need to distinguish between same-named records in different environments. Consuming a specific record type from a stream containing multiple Avro types. `schema_subject_name` is usually full qualified record name like `com.x.y.z.RecordA`|
0 commit comments