[
https://issues.apache.org/jira/browse/BEAM-1819?focusedWorklogId=416078&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-416078
]
ASF GitHub Bot logged work on BEAM-1819:
----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Apr/20 22:57
Start Date: 04/Apr/20 22:57
Worklog Time Spent: 10m
Work Description: reuvenlax commented on issue #11154: [BEAM-1819] Key
should be available in @OnTimer methods
URL: https://github.com/apache/beam/pull/11154#issuecomment-609100632
@steveniemitz in principle, removing a state cell is absolutely a
backwards-incompatible change, just like removing a GroupByKey is (for the
latter, the Dataflow requires the user to explicitly allow the deletion on
update). There are multiple things that can go wrong if a state cell is removed
accidentally. In practice, I'm not 100% sure if Dataflow or any other runner
currently validates compatibility at the state cell level or not.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 416078)
Time Spent: 15.5h (was: 15h 20m)
> Key should be available in @OnTimer methods
> -------------------------------------------
>
> Key: BEAM-1819
> URL: https://issues.apache.org/jira/browse/BEAM-1819
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Thomas Groh
> Assignee: Shehzaad Nakhoda
> Priority: Major
> Time Spent: 15.5h
> Remaining Estimate: 0h
>
> Every timer firing has an associated key. This key should be available when
> the timer is delivered to a user's {{DoFn}}, so they don't have to store it
> in state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
