I've 2 topics with the exact same schema. The schema registry shows 2 distinct subjects (one per topic value). But since the schema are the same, the registry (in my case redpanda) only uses one id for both.
The API returns the 2 subjects as expected
$ curl http://localhost:8081/schemas/ids/14/versions | jq .
[
{
"subject": "topic-v3-value",
"version": 3
},
{
"subject": "topic-v2-value",
"version": 3
}
]But when displaying a topic, the UI only take the first one in consideration and doesn't check that the subject concerns a topic. In the screenshot below, the topic topic-v2 displays the subject topic-v3-value. And when I click on it, of course I go to the wrong subject.
I know this depends on the naming strategy but I would expect the UI to follow the TopicNameStrategy if possible.
I've 2 topics with the exact same schema. The schema registry shows 2 distinct subjects (one per topic value). But since the schema are the same, the registry (in my case redpanda) only uses one id for both.
The API returns the 2 subjects as expected
But when displaying a topic, the UI only take the first one in consideration and doesn't check that the subject concerns a topic. In the screenshot below, the topic
topic-v2displays the subjecttopic-v3-value. And when I click on it, of course I go to the wrong subject.I know this depends on the naming strategy but I would expect the UI to follow the
TopicNameStrategyif possible.