masongup-mdsol opened a new issue, #164: URL: https://github.com/apache/avro-rs/issues/164
While I was working with the `GenericSingleObjectReader` and `GenericSingleObjectWriter` objects to read and write the Kafka messages that the other tools in my company are using, I noticed that they are currently hard-coded to use a specific header fingerprint format: [reader](https://github.com/apache/avro-rs/blob/main/avro/src/reader.rs#L511-L527), [writer](https://github.com/apache/avro-rs/blob/main/avro/src/reader.rs#L511-L527). The messages that I am working with use an AWS Glue Schema Registry and [the corresponding header format](https://lenses.io/blog/2023/04/aws_glue_schema_registry_that_binds_apache_kafka/) on messages. As a result of this, to handle these messages, I have to write a wrapper for the reader which reads out the Glue schema UUID manually, strips out those bytes, and adds on the header that the library expects, and for the writer that strips out the library-generated header and generates a new Glue header for the message. This all seems cumbersome to me. Are there any plans and/or interest to support either completely bare Avro data or proper interpretation of other types of message headers? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
