You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use Redpanda Schema Registry for sending records with JSON Schema.
Schema is generated from Pydantic Classes.
I'm getting error
confluent_kafka.schema_registry.error.SchemaRegistryError: bundled schema with mismatched dialect 'https://json-schema.org/draft/2020-12/schema#' for id key (HTTP status code 422, SR code 422)
What should have happened instead?
Schema should be registered. Confluent Schema Registry can handle it properly.
All the validators say its correct JSON Schema.
How to reproduce the issue?
Download attached json file
Publish it to redpanda
Example request: curl -X POST -H "Content-Type: application/vnd.schemaregistry.v1+json" -d @wrong-schema.json http://redpanda.redpanda.svc:8081/subjects/test-json-wrong-value/versions
See error: {"error_code":422,"message":"bundled schema with mismatched dialect 'https://json-schema.org/draft/2020-12/schema#' for id key"}
maver1ck
changed the title
SchemaRegistryError: bundled schema with mismatched dialect
[v24.3.3] SchemaRegistryError: bundled schema with mismatched dialect
Jan 28, 2025
Version & Environment
Redpanda version: (use
rpk version
): v24.3.3confluent-kafka==2.8.0
What went wrong?
I'm trying to use Redpanda Schema Registry for sending records with JSON Schema.
Schema is generated from Pydantic Classes.
I'm getting error
What should have happened instead?
Schema should be registered. Confluent Schema Registry can handle it properly.
All the validators say its correct JSON Schema.
How to reproduce the issue?
Example request:
curl -X POST -H "Content-Type: application/vnd.schemaregistry.v1+json" -d @wrong-schema.json http://redpanda.redpanda.svc:8081/subjects/test-json-wrong-value/versions
{"error_code":422,"message":"bundled schema with mismatched dialect 'https://json-schema.org/draft/2020-12/schema#' for id key"}
Additional information
wrong-schema.json
JIRA Link: CORE-8936
The text was updated successfully, but these errors were encountered: