Skip to content

Schema registry #76

New issue

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

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

Already on GitHub? # to your account

Open
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

jrevillard
Copy link
Contributor

@jrevillard jrevillard commented Aug 13, 2021

Dear all,

Here is an MR for #50.

This work is based on the POC that was done by @Twb3:

  • I removed the specific authentication variables as this is already implemented by the standard schema registry client
  • I added PROTOBUFFER and JSON type
  • I removed the Jsondiff stuff to rely on the pure schema registry libs
  • Schemas can be embedded or in separate files
  • I update graddle and groovy to ease the IDE integration (Eclipse)
  • I did most of the tests I think (I did not test the schema registry connection...)
  • All the registered schemas have a proper "compatibility" and do not rely on the default one
  • Limitation: you cannot update the compatibility after having registered the subject
  • Plan serialization is modified and I don't know why !!! ( spaces before : and dots between empty [ ])
  • schemas blacklist is implemented

What should still be done in my opinion if somebody want to help:

  • update documentation
  • add --skip-schemas command option (as for acls) -> if schema registry url not provided, then schemas management skip
  • add the possibility to update compatibility
  • test schema registry connection options

Best,
Jerome

@jrevillard jrevillard force-pushed the schema-registry-github branch 2 times, most recently from c321e25 to 322120d Compare August 17, 2021 10:56
@jrevillard jrevillard force-pushed the schema-registry-github branch 2 times, most recently from 975df16 to 126f15e Compare August 25, 2021 15:02
@jrevillard jrevillard force-pushed the schema-registry-github branch from 126f15e to 7749e13 Compare April 21, 2022 17:42
@pfeigl
Copy link

pfeigl commented Jan 13, 2023

Too bad this seemingly never made it into main sofar. Very much looking forward to this functionality

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants