aromanenko-dev commented on issue #27635: URL: https://github.com/apache/beam/issues/27635#issuecomment-1660712228
@Gadiguibou > I think I could. Unfortunately Kryo v4 and v5 [are not binary compatible](https://github.com/EsotericSoftware/kryo/wiki/Migration-to-v5). How is this usually handled in Beam? Is this even a concern? In Beam, we tend to avoid the breaking changes that may affect users after Beam upgrade, especially, if it may cause potentially data loss or corruption, as much as we can. Since Beam doesn't support "hot" upgrade on the fly while running a pipeline, and Kryo extension is used only as a `KryoCoder` (correct me if I'm wrong) then serialised data should not be stored somewhere after pipeline is stopped. Also, I hope we don't expose any Kryo API to users as well. So, this means that it should be safe. Regarding the adding support for Java records to SchemaCoder - I believe it deserves a dedicated issue/PR. Btw, I'm not sure that we have an active maintainer for this extension but I'll ping @dmvk, who initially worked on this and Euphoria (that heavily uses `KryoCoder`), for additional comments. -- 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]
