yittg commented on issue #4806: A Pulsar producer should be able to produce messages of different schemas URL: https://github.com/apache/pulsar/issues/4806#issuecomment-524901586 @sijie i have a similar scenario, a producer with AUTO_PRODUCE_BYTES schema(AVRO inner schema in schema registry) to send bytes encoded with AVRO. After updating a new compatible schema, the producer will use older schema when sending bytes, even if they are encoded with newer schema, on the contrary, a new producer will use newer schema when sending bytes encoded with older schema. Is there any plan or design in progress? Maybe we can drop the ability to control the schema version to the message level. The producer would check the schema version of message and load it from the registry if it is different from the current producer.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
