You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:04 UTC

[jira] [Updated] (BEAM-11193) Fix KeyedTimerData

     [ https://issues.apache.org/jira/browse/BEAM-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-11193:
-----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> 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: P3
>          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.20.1#820001)