Open JohnPreston opened 3 days ago
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 :shrug:
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?
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