RustedBones commented on pull request #16271: URL: https://github.com/apache/beam/pull/16271#issuecomment-1007453667
There are no breaking changes to the `AvroCoder` directly. I'd like to add the possibility to create coders using datum factories. Users could customize (de)serialization and enable more advanced avro features (eg. [BEAM-9144](https://issues.apache.org/jira/browse/BEAM-9144) to get reader and writer supporting both java.time and joda.time) The breaking changes are: - Some `AvroIO` API requiring to pass class type - `AvroCoderCloudObjectTranslator` is not able so serialize custom factories Maybe we should do as for the `AvroGenericCoder` and give specialized implementation for the `AvroSpecificCoder` and `AvroReflectCoder`. Change visibility of the `AvroCoder` so users can extend and create their own. Only provide the `CloudObjectTranslator`, for `AvroGenericCoder`, `AvroSpecificCoder` and `AvroReflectCoder` and let users provider their own translator if they use a custom avro coder -- 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]
