So basically, if you have a topic called "my-topic", the schema will be looked up in the schema registry by the key "my-topic-key" for the key-schema, and "my-topic-value" for the value-schema.

At my company, less than half of the topic owners have adhered to this convention so we have the same problem you have with no schemas in the catalog for those topics.

It looks like you can override it in the kafka source config though, on a per topic level.

There is also an example a bit further down.

Note, I'm not working for Acryl/Datahub so take my replies for best effort answers.

I have read the doc

but not able to understand the following topic_subject_map: _# Defines both key & value schema for topic 'my_topic_1'_ "my_topic_1-key": "io.acryl.Schema1" "my_topic_1-value": "io.acryl.Schema2" _# Defines only the value schema for topic 'my_topic_2' (the topic doesn't have a key schema)._ "my_topic_2-value": "io.acryl.Schema3"