Unable to access confluent compatible schema from apicurio ccompat v6
See original GitHub issueApicurio version: 2.2.3.Final Running on Docker environment using: apicurio/apicurio-registry-sql:2.2.3.Final
curl -X GET -H "Accept:application/json" http://hostname/apis/ccompat/v6/subjects/<subject-name>/versions/latest
This gives 400 with response {"message":"Failed to discover artifact type from content.","error_code":0}
and in the logs I can see [Fatal Error] :1:1: Content is not allowed in prolog.
This is happening only for a few schemas.
The same schema can be accessed using the below API for all my schemas.
curl -X GET -H "Accept:application/json" http://hostname/apis/ccompat/v6/schemas/ids/19
Issue Analytics
- State:
- Created a year ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
API ccompat v6 not returning artifact · Issue #1593 - GitHub
I'm trying to configure kowl with APICurio which requires a Confluence Schema Registry compliant API. I see a list of schemas in the...
Read more >Using Apache NiFi's ConfluentSchemaRegistry with Apicurio ...
The ccompat API should be compatible to Confluent. But when i run the NiFi pipeline i get the following error, that the schema...
Read more >Schema Registry API Reference | Confluent Documentation
The Schema Registry server can enforce certain compatibility rules when new schemas are registered in a subject. These are the compatibility types:.
Read more >Use External Schema Registry with MSK Connect - Cevo
It provides multiple APIs and one of them is compatible with the Confluent schema registry (/apis/ccompat/v6). We'll use this API as we plan...
Read more >Apache Kafka | Programmatic Ponderings
Replace Apache Hive with AWS Glue Data Catalog, a fully-managed Hive-compatible metastore. Replace Apicurio Registry with Confluent Schema Registry or AWS Glue ...
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
I have found the issue. When the type is being discovered getting the schema, the references were not passed down and it was failing because of that. I have created a PR that solves this problem.
There are no updates since it’s pretty difficult to reproduce the issue without the problematic schema. Nothing should be done to map a schema to a subject (if the subject does not exist, it will be created when the schema is created). If you provide more details (schema being used, schema type etc), I can try to reproduce the issue.