-
Notifications
You must be signed in to change notification settings - Fork 250
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
Registration of schemas with same artifactId and different groupId causes error in api #1501
Comments
this looks like a bug
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If two schemas with same artifactId and different groupId are registered, then api returning schema by globalId (apis/registry/v2/ids/globalIds/{globalId}) fails for globalId of both schemas with error:
{"message":"No artifact with ID '120' in group 'null' was found.","error_code":404,"detail":"io.apicurio.registry.storage.ArtifactNotFoundException: No artifact with ID '120' in group 'null' was found
...
This is a serious issue because registration of a schema can cause failure in a communication for already registered schema in a completely different groupId used by different teams.
Tested with version 2.0.0.Final and kafka sql storage. The same scenario worked OK with version RC1 and kafka streams storage.
The text was updated successfully, but these errors were encountered: