TopicRecordNameStrategy is a hybrid Schema Registry subject-naming strategy. It associates each subject with a specific topic while retaining the record’s fully qualified name, allowing multiple event types to coexist in one topic and evolve independently. section 6.4.3
Client events in one topic
Registering com.example.ClientEvent for the CLIENTS topic produces the subject CLIENTS-com.example.ClientEvent. Other event types can share CLIENTS under distinct subjects, while each schema evolves independently within that topic. section 6.4.3
Listing 6.10 An example of the client event in Avro format
{
"type": "record",
"name": "ClientEvent",
"namespace": "com.example",
"fields": [
{
"name": "eventId",
"type": "string",
"doc": "Unique identifier for the event"
},
{
"name": "eventType",
"type": "string",
"doc": "Type of event (e.g., 'ClientCreated', 'ClientUpdated')"
},
{
"name": "timestamp",
"type": "long",
"logicalType": "timestamp-millis",
"doc": "Event timestamp in milliseconds"
},
{
"name": "clientId",
"type": "string",
"doc": "Unique identifier for the client"
},
{
"name": "clientName",
"type": "string",
"doc": "Name of the client"
}
]
}
An Avro ClientEvent record illustrates the fully qualified name and the eventId, eventType, timestamp, clientId, and clientName fields carried by the example. section 6.4.3

