-
Notifications
You must be signed in to change notification settings - Fork 13
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
encountered an issue try to consume the messages and get the schema, the message from Apicurio does not include the field "schemaType" #14
Comments
Thanks for taking this issue. please help us once this issue fix. |
This is related to this |
Hi @kmandal-volvo, When you say "That field is not present in the response we get from Apicurio" at which endpoint are you referring? According to the API reference, Confluent is not returning the That said, I've realized that we're missing the In any case, thanks for your interest! |
@carlesarnal quickly looking at this, because schematype and references are not returned in the endpoints, you can see this clearly in confluent code....then Confluents serdes cannot work as they need to know the type is protobuf and the linked referenced schemas for complex proto schemas with imports. |
yeah, this can be considered a bug in apicurio. We don't have these fields as they're not documented in the API reference. That said, they're clearly present in the code, so I will revisit this and try to fix it, thanks. |
Closing in favour of this since this is a bug in Apicurio Registry Compatibility API. |
I do understand from the conversation but How I will know which version or release Apicurio will fix the issue |
This issue with the |
When we can expect this release of Apircurio Registory |
You have a RC1 of 2.1.0 available here. |
We are using serializer and deserializer for protobuf components from Confluent since they are compatible with JRE 8. I have pointed our producer and consumer application to use endpoint http://localhost/apis/ccompat/v6 since that API endpoint is meant to be compatible with Confluent. Unfortunately, we have encountered an issue that prevents us from getting forward. When the consumer application tries to retrieve the schema it expects a JSON message that also includes the field “schemaType”, this field is needed by the Confluent deserializer to know that is should deserialize the records on the topic as PROTOBUF-messages. That field is not present in the response we get from Apicurio. If the schemaType-field is missing it will assume that the schema is of type “AVRO”. You can see it ourselves in below response from the CMD:
Apicurio Schema registry version we are using quay.io/apicurio/apicurio-registry-kube-sync:latest-snapshot and quay.io/apicurio/apicurio-registry-mem:2.0.1.Final.
The text was updated successfully, but these errors were encountered: