Confluent Compatibility Issue with subject version
See original GitHub issueHello, Looks like Apicurio registry is not fully compatible with Confluent. Confluent API schema registry uses the version -1 as a special id for the latest version.
When using the Confluent Schema Registry plugin and a version is not provided, it fallback on -1 and sends a request similar the one below to Apicurio:
https://apicurio-service/apis/ccompat/v6/subjects/my-subject-value/versions/-1
The following error is observed:
{
"message": "Illegal version format: -1",
"error_code": 0
}
I was expecting that Apicurio handle the -1 similarly.
I have also noticed that there is no Maven plugin allowing to register/test compatibility ect… of schemas.
Best,
Mouad
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Schema Evolution and Compatibility - Confluent Documentation
The compatibility type determines how Schema Registry compares the new schema with previous versions of a schema, for a given subject.
Read more >get error in Schema Registry Quickstart demo step to update ...
Hi CL,. One more note - under the hood, schema registry persists compatibility changes (as well as schemas) to a Kafka topic, "_schemas";...
Read more >Schema Registry Incompatible - apache kafka - Stack Overflow
You'd check the schemas using the subject and version number(s) ... The Confluent Schema Registry default compatibility type BACKWARD is ...
Read more >Schema Compatibility | Schema Registry 101 - YouTube
Also, learn how the Confluent Schema Registry verifies schema compatibility ... compatibility modes that you assign to each schema subject.
Read more >Evolving Schemas with Schema Registry | Data Arena - Medium
A topic can have schemas for keys, values, or both. ... The Confluent Schema Registry compatibility modes are divided into two groups that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you!
I have tried to open this ticket https://github.com/confluentinc/schema-registry/issues/2394 on their side, it explains the behaviour, however I wasn’t sure if it was expected on their side and I closed it and opened this one.
What do you think ?