[
https://issues.apache.org/jira/browse/BEAM-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16729615#comment-16729615
]
Jeff Klukas commented on BEAM-3616:
-----------------------------------
Here's an additional relevant thread that discusses the need for versioning
coders in order to allow adding new fields to existing classes:
[https://lists.apache.org/thread.html/d9a780bd5203b5188168d6fb461e6822dcac4314fd4530873876ec3c@%3Cdev.beam.apache.org%3E]
> Ensure coders are updatable partially in a cluster (aka add versions to
> coders)
> -------------------------------------------------------------------------------
>
> Key: BEAM-3616
> URL: https://issues.apache.org/jira/browse/BEAM-3616
> Project: Beam
> Issue Type: Improvement
> Components: beam-model
> Reporter: Romain Manni-Bucau
> Priority: Major
> Fix For: 3.0.0
>
>
> Follow up ticket for the following discussion:
> https://lists.apache.org/thread.html/f3b2daa740075cc39dc04f08d1eaacfcc2d550cecc04e27be024cf52@%3Cdev.beam.apache.org%3E
> Long story short: seems being able to update a live stream is a constraint
> beam must address. This implies no change in coder serialization. To do it
> the only way is to put a marker (like a version) otherwise the live update
> will be broken if part of a cluster is updated only.
> This task is about ensuring we support it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
