In our Kafka client we use Vulcan, and we have automatic schema registration disabled for some topics because we're not the owners.
We noticed that when Vulcan tries to look up the schema from the schema registry, when it's going to send a message, it requires exact schema equality with the schema that follows from our case classes; even e.g. the ordering of fields within a message should be the same, or the occurrence of doc elements.
Why does Vulcan use exact equality in the schema lookup and not semantic compatibility?
In our Kafka client we use Vulcan, and we have automatic schema registration disabled for some topics because we're not the owners.
We noticed that when Vulcan tries to look up the schema from the schema registry, when it's going to send a message, it requires exact schema equality with the schema that follows from our case classes; even e.g. the ordering of fields within a message should be the same, or the occurrence of doc elements.
Why does Vulcan use exact equality in the schema lookup and not semantic compatibility?