-
Notifications
You must be signed in to change notification settings - Fork 20
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
BUG: CRUD a topic with a schema, using a large schema registry, fails both schema & topic management #498
Comments
JohnPreston
changed the title
CRUD a topic with a schema, using a large schema registry, fails both schema & topic management
BUG: CRUD a topic with a schema, using a large schema registry, fails both schema & topic management
Nov 25, 2024
PS: if I split the schema and the topic to be in different files, then Jikkou seems happy to deal with the schema, although that's taking a long, long time to complete 🤷 EDIT: I am guessing, jikkou is importing all the subjects & schemas to do the diff, but it could probably do that just for the subject name instead of a bulk? |
fhussonnois
added a commit
that referenced
this issue
Nov 26, 2024
fhussonnois
added a commit
that referenced
this issue
Nov 29, 2024
fhussonnois
added a commit
that referenced
this issue
Nov 30, 2024
fhussonnois
added a commit
that referenced
this issue
Dec 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When I have a topic and a schema defined in my resource file, and the schema registry I use has 1000s of subjects, the commands A/ take a very long time B/ fail with a NPE on topic management.
Additional info: I have observed, via DEBUG, that the client seems to list all the subjects, and retrieve all the schemas, every single time. Not sure why that is. The SR management should only mean to retrieve the existing subject, versions, if not found, create the first version, if found, try update to have a new version with the new schema definition, along with checking compatibility, and possibly setting compatibility on the subject, etc. But it does not need to pull all the schemas.
To Reproduce
Try to create/update a topic on a cluster and small (empty/few) schema registry -> Works
Try the same with a schema registry that has 1000s of subjects -> fails with NPE below
Remove/comment out the Schema from the resource file-> works fine for the topic management.
Expected behavior
My topic is created/updated and the operations for the schema should work too.
Screenshots/Configs
Configuration is as you'd expect, with SASL_SSL/PLAIN and the registry details set to use Confluent Cloud URL, basic auth.
Runtime environment
The text was updated successfully, but these errors were encountered: