pub enum SubjectNameStrategy {
TopicName,
RecordName,
TopicRecordName,
}Expand description
Subject name strategies used in registering key and value schemas with the schema registry.
Variants§
TopicName
The subject name is derived directly from the Kafka topic name.
For update formats with both key and value components, use subject names
{topic_name}-key and {topic_name}-value for key and value schemas respectively.
For update formats without a key (e.g., raw), publish value schema
under the subject name {topic_name}.
Only applicable when using Kafka as a transport.
RecordName
The name of the SQL relation that the schema is derived from is used as the subject name:
- the SQL view name for the message value schema.
- the SQL index name for the message key schema.
TopicRecordName
Combines both the topic name and the record name to form the subject.
For update formats with both key and value components, use subject names
{topic_name}-{record_name}-key and {topic_name}-{record_name}-value for
key and value schemas respectively.
For update formats without a key (e.g., raw), publish value schema
under the subject name {topic_name}-{record_name}.
{record_name} is the name of the SQL view or index that this connector
is attached to.
Only applicable when using Kafka as a transport.
Trait Implementations§
Source§impl Clone for SubjectNameStrategy
impl Clone for SubjectNameStrategy
Source§fn clone(&self) -> SubjectNameStrategy
fn clone(&self) -> SubjectNameStrategy
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source. Read more