Skip to content

Commit e185a2f

Browse files
authored
refine kafka schema registery subject name, take 2 (#594)
1 parent 251b492 commit e185a2f

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/kafka-schema-registry.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ The `subject_name_strategy` determines how the stream looks up schemas in the re
4242

4343
| Strategy | Behavior | Derived Subject Name | Typical Use Case |
4444
| :--- | :--- | :--- | :--- |
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. |
4646
| **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` |
4747
| **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`|
4848

0 commit comments

Comments
 (0)