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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: