Skip to content
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

Unrecognized field: schemaType (HTTP status code 422, SR code 422) #1876

Open
7 tasks done
ffissore opened this issue Dec 18, 2024 · 2 comments
Open
7 tasks done

Unrecognized field: schemaType (HTTP status code 422, SR code 422) #1876

ffissore opened this issue Dec 18, 2024 · 2 comments

Comments

@ffissore
Copy link
Contributor

Description

We run schema registry 5.1.4 (confluentinc/cp-schema-registry:5.1.4), which returns 422 when registering schemas using the latest confluent-kafka version, 2.6.2.
The culprit is PR #1852, specifically these lines: they are hard to catch because they buried under 12000 changed lines

How to reproduce

Run cp-{kafka,zookeeper,schema-registry}-5.1.4 and try registering a schema.

Checklist

Please provide the following information:

  • confluent-kafka-python and librdkafka version (confluent_kafka.version() and confluent_kafka.libversion()): ('2.6.2', 33948160), ('2.6.1', 33948159)
  • Apache Kafka broker version: 2.1.1 (cp-kafka:5.1.4)
  • Client configuration: {...}: unrelated
  • Operating system: unrelated
  • Provide client logs (with 'debug': '..' as necessary): schema registry client doesn't log, however, this is the body of the request sent by it {"schema": "{\\"type\\": \\"record\\", \\"name\\": \\"HelloWorldValue\\", \\"fields\\": [{\\"type\\": \\"string\\", \\"name\\": \\"hello\\"}]}", "schemaType": "AVRO", "references": []}
  • Provide broker log excerpts: unrelated
  • Critical issue: no but it prevents us from upgrading the library
@rayokota
Copy link
Member

@ffissore , are you able to upgrade to CP 5.5+?

@ffissore
Copy link
Contributor Author

I'm not. We know we are lagging behind but the migration/upgrade has always been postponed and I have no idea when it will be prioritised.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants