Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure Karapace compatibility with Confluent API #916

Open
1 task
gscher opened this issue Jul 16, 2024 · 0 comments
Open
1 task

Ensure Karapace compatibility with Confluent API #916

gscher opened this issue Jul 16, 2024 · 0 comments

Comments

@gscher
Copy link

gscher commented Jul 16, 2024

What is currently missing?

It seems like that with the latest releases, Confluent included some breaking changes on the Schema Registry API level and their open source Kafka clients as part of a data contract feature.
The consequence is that for example their Kafka .Net client (https://github.com/confluentinc/confluent-kafka-dotnet) in version 2.5.0 is no longer compatible with Karapace.

What I have seen when comparing schema registry API calls is that the call to register a new schema now includes additional fields such as Metadata and RuleSet which Karapace can't handle right now and therefore the entire schema registration crashes.

https://docs.confluent.io/platform/current/schema-registry/develop/api.html#post--subjects-(string-%20subject)-versions

How could this be improved?

It would be great if Karapace stays compatible also to newer schema registry client versions. Maybe a quick win would be to accept the additional fields on the REST API level, but just ignore them for the time being?

Is this a feature you would work on yourself?

  • I plan to open a pull request for this feature
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant