-
-
Notifications
You must be signed in to change notification settings - Fork 659
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
subject does not have subject-level compatibility configured #1098
Comments
Can you try with last version ? 0.21.0 please ? |
Thanks for getting back to me @tchiotludo . I'm still experiencing the same issue on 0.21.0 |
Looking at quickly, the pr here only remove the error from akhq but still send the query without |
Thanks a lot @tchiotludo, that fixed it! 🎉 |
Hi @tchiotludo, do you perhaps have an idea of when a docker image (version tagged) will be ready with this fix? |
@juliangovender you can use the dev image that is already available |
Hi,
I am seeing errors in my schema-registry kubernetes pod when I use AKHQ to access my schema registry:
io.confluent.rest.exceptions.RestNotFoundException: Subject [] does not have subject-level compatibility configured
The schemas still load correctly in the UI and there are no errors on the UI / akhq pod, only on the schema registry pod when accessed by akhq. When accessed by my backend, I see 200's on the schema registry pod logs.
I understand that defaultToGlobal=true querystring has been added in v0.18. I am currently using akhq:0.20.0
The text was updated successfully, but these errors were encountered: