SamStentz commented on issue #32559:
URL: https://github.com/apache/beam/issues/32559#issuecomment-2374686579
Im also hitting slightly different behavior when I deploy a pipeline to the
GCP dataflow runner.
There, I see after an indeterminate count of retries, reading of state in
OnTimer shows the state has been wiped (the below snippet returns tcp = false).
```golang
tc, tcp, err := fn.TimerCount.Read(sp)
if err != nil || !tcp {
panic("couldn't read TimerCount state")
}
```
Am I incorrect in assuming that if my ProcessElement function always sets
state values, then OnTimer will always have that value populated? For context,
I am trying to add this timer per every element in a PCollection, so I am
adding a uuid key. Regardless, I wouldn't expect the behavior to result in a
wiped State.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
