[GitHub] [beam] aromanenko-dev commented on issue #27635: [Feature Request]: Upgrade Kryo version of Kryo Java extension

["aromanenko-dev (via GitHub)" <gi...@apache.org>]

aromanenko-dev commented on issue #27635:
URL: https://github.com/apache/beam/issues/27635#issuecomment-1706955967

   @je-ik I'm sorry for delay with an answer, I was on vacation.
   
   I agree that we have to do our best to avoid breaking changes (I'm one of the person who always propose to deprecate things before) and I mentioned this before, but I don't remember any "official" (or previously agreed) policy about such a support of Beam upgrade on the fly, and particularly, for streaming pipelines. So, do we need to guarantee a Coder compatibility between Beam releases since Beam coders are supposed to be used "inside" a pipeline? 
   
   > I came across this when validating 2.50.0 RC (this is even a code breaking change, beacuse the KryoCoder 'leaks' kryo API)
   
   Did you have a compilation time or runtime issue? Could you provide more details on this?
   
   Also, as a side note: 
   It leads us to the question - should we even make Kryo provided and let users to choose which versions to use?
   


-- 
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: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org