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

Can't evolve schema after setting per-topic compatibility #70

Open
jurgispods opened this issue Jul 30, 2018 · 0 comments
Open

Can't evolve schema after setting per-topic compatibility #70

jurgispods opened this issue Jul 30, 2018 · 0 comments

Comments

@jurgispods
Copy link

jurgispods commented Jul 30, 2018

Evolving schemas with the Schema Registry UI usually is a fairly simple and convenient process.

However, using version 0.9.4 together with Confluent Platform 4.0, the following steps lead to a situation where I can't remove fields from a previously created schema.

  1. Create a new schema
  2. Set compatibility level to NONE (my global level is BACKWARD)
  3. Edit schema, remove one of the fields, click "Validate", the tooltip "You can now evolve your schema" displays as expected
  4. Click "Evolve schema"

The UI seems to accept the schema evolution and doesn't display an error, but it still shows the previous schema version with the exact schema as before. Nothing changed.

I am able to evolve the schema correctly and get a new version of my schema if I just add a field.

The output of `kafka-configs --zookeeper {myzookeeper} --entity-type topics --entity-name {mytopic} --describe is empty, although the compatibility level was changed according to the UI.

Any ideas?

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