Skip to content

SchemaRegistrySerde: Avro deserialization without magic byte using lookup by topic name as fallback like in serialization #4520

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

Open
2 tasks done
1-alex98 opened this issue Mar 4, 2025 · 1 comment · May be fixed by #4521
Labels
status/triage Issues pending maintainers triage type/feature A new feature

Comments

@1-alex98
Copy link

1-alex98 commented Mar 4, 2025

Issue submitter TODO list

  • I've searched for an already existing issues here
  • I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?

I have a producer on Kafka. I have no control about the producer and the producer does not set the magic byte and schema id in avro that would tell a consumer what schema to use. However I want to inspect the messages in Kafka UI.

Describe the feature you're interested in

I want to be able to set the correct schema.
When Serializing messages the code in SchemaRegistrySerde has a look into the registry using the topic name.
Suggestion:
When Deserializing:

  1. Have a look at magic byte and schema ID
  2. If no schema ID set have a look in the registry using the topic name and try this schema
  3. Fail otherwise

-> Suggestion add step 2

Describe alternatives you've considered

Setting the magic bytes and schema ids in messages. However in a lot of cases the read does not control the producer.
Setting the correct schema via UI.

Version you're running

Applies to all versions

Additional context


Currently only reads the schema from the message it-self

@1-alex98 1-alex98 added status/triage Issues pending maintainers triage type/feature A new feature labels Mar 4, 2025
Copy link

github-actions bot commented Mar 4, 2025

Hello there 1-alex98! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀

@1-alex98 1-alex98 changed the title Avro deserialization without magic byte SchemaRegistrySerde Avro deserialization without magic byte using lookup by topic name as fallback like in serialization Mar 4, 2025
@1-alex98 1-alex98 changed the title SchemaRegistrySerde Avro deserialization without magic byte using lookup by topic name as fallback like in serialization SchemaRegistrySerde: Avro deserialization without magic byte using lookup by topic name as fallback like in serialization Mar 4, 2025
1-alex98 added a commit to 1-alex98/kafka-ui that referenced this issue Mar 4, 2025
Avro deserialization without magic byte using lookup by topic name as fallback like in serialization
Closes provectus#4520
@1-alex98 1-alex98 linked a pull request Mar 4, 2025 that will close this issue
13 tasks
1-alex98 added a commit to 1-alex98/kafka-ui that referenced this issue Mar 4, 2025
Avro deserialization without magic byte using lookup by topic name as fallback like in serialization
Closes provectus#4520
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/triage Issues pending maintainers triage type/feature A new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant