[
https://issues.apache.org/jira/browse/BEAM-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298982#comment-17298982
]
Beam JIRA Bot commented on BEAM-11193:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Fix KeyedTimerData
> ------------------
>
> Key: BEAM-11193
> URL: https://issues.apache.org/jira/browse/BEAM-11193
> Project: Beam
> Issue Type: Task
> Components: runner-samza
> Reporter: Ke Wu
> Priority: P2
> Labels: stale-P2
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> outputTimestamp was added to KeyedTimerDataCoder and encoded in the middle of
> stream. This is not a backward compatible changes for stateful jobs.
> All new fields in KeyedTimerData should be appended to the last in
> KeyedTimerDataCoder
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
