Closed sabbyanandan closed 3 years ago
We are going to keep the schema registry code unmoved from its current location for 3.1. Post 3.1, we might consider moving it and isolating it to the Kafka binder, but that needs further consideration of a few moving targets. Closing this issue now. We will create more issues or an epic in the due course for further such actions.
The goal here is to bring
ConfluentSchemaRegistryClient
closer to the Kafka binder, so it is easy for users to costume, and one less dependency to worry about.