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

Add support for retrieving the AWS glue schema information from message headers #296

Open
vlidna opened this issue Sep 8, 2023 · 3 comments
Labels
enhancement New feature or request research Needs research

Comments

@vlidna
Copy link

vlidna commented Sep 8, 2023

Currently the AWSKafkaAvroSerializer/Deserializer encodes the schema version id into the body of the message. Now that Kafka supports message headers, it would be nice to support storing the schema version id in the message header for easier integration across languages that are not only using Java.

For example, I have producers and consumers in javascript and python and it is easier to just put the schema version id into the message header than it is to couple these to the mechanism used in the AWSKafkaAvroSerializer/Deserializer. If these supported setting and getting the schema version id in the message headers then I would not have to duplicate this serialization code in my various clients.

@YangSan0622 YangSan0622 added enhancement New feature or request PR welcome Users are welcome to submit PR labels Sep 11, 2023
@woile
Copy link

woile commented Sep 15, 2023

I would love to have support for headers in the headers. And even better would be to have support for cloudevents. Are there any plans to do so?

@blacktooth
Copy link
Contributor

And even better would be to have support for cloudevents

What do you mean by cloudevents? Can you please clarify?

@blacktooth blacktooth added research Needs research and removed PR welcome Users are welcome to submit PR labels Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request research Needs research
Projects
None yet
Development

No branches or pull requests

5 participants