SR: 404 for compatibility request for non-confluent SR impl #809
Labels
area/sr
Schema Registry
scope/backend
Related to backend changes
status/triage/completed
Automatic triage completed
type/bug
Something isn't working
Issue submitter TODO list
main
-labeled docker image and the issue still persists thereDescribe the bug (actual behavior)
When I navigate to the Schema Registry tab, in the Browser Developer Tool, I see that the request to retrieve the schema registry returns a 200 with a response body of my schemas.
However, after that it calls
/schemas/compatibility
, the response body returns a404 not found
. I noticed the API appended an extra/
at the end resulting in/config/
in the response bodyBased on the confluent documentation: https://docs.confluent.io/platform/7.8/schema-registry/develop/api.html#config
It looks like the official confluent api endpoint is using
/config
for thePUT
and theGET
request. Is it possible to get the API changed to reflect that as well?I see that the swagger API has
/config/
listed:https://github.com/kafbat/kafka-ui/blob/main/contract/src/main/resources/swagger/kafka-sr-api.yaml#L168
Prior, I was using
ghcr.io/kafbat/kafka-ui:v1.0.0
and the above issue didn't seem to be a problem when it came to rendering the schemas on the UI.Expected behavior
I expected the Schema Registry to list my schemas on the UI
Your installation details
app version: 4cf17a0 v1.1.0
Image using:
ghcr.io/kafbat/kafka-ui:v1.1.0
.I've deployed the application via helm chart that I've created.
Steps to reproduce
Screenshots
Logs
GET request
Response header:
Additional context
I'm not too sure of the functionality of the project, but I tried the changes locally and it seems to work.
I'm unsure of the side effects/regression it could cause by changing the API.
Steps:
/config/
to/config
inkafka-sr-api.yaml
./mvnw clean install -Dmaven.test.skip=true -Pprod
The text was updated successfully, but these errors were encountered: