[
https://issues.apache.org/jira/browse/BEAM-10660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199678#comment-17199678
]
Robert Burke commented on BEAM-10660:
-------------------------------------
Bolstered the description a little. This is definitely an "end of the line"
type feature. As I've put into the description, there are many much smaller
stpeping stones for us to handle that would be easier to add than timers, and
are almost required before considering timers.
> [Go SDK] Implement Timer support
> --------------------------------
>
> Key: BEAM-10660
> URL: https://issues.apache.org/jira/browse/BEAM-10660
> Project: Beam
> Issue Type: New Feature
> Components: sdk-go
> Reporter: Robert Burke
> Priority: P2
>
> There's presently no mechanism to specify timers in the Go SDK, or use them
> at all. The work would be designing the user facing code, and mechanisms, and
> plumbing through timers properly. For ecample they can't be conflicting with
> other user facing constructs like Emitter functions and iterator functions.
> However there's an abundance of work to handle before starting to deal with
> state and timers though.
> While timers should work in batch, they're commonly more appropriate for
> streaming which the SDK doesn't support very well at the moment. DoFns need
> to be able to Self Checkpoint in order to behave as a streaming source (early
> checkpointing allows a bundle to self terminate, so it can be rescheduled
> later or as a minor way to split to multiple workers.). We should also
> implement Triggers and Advanced/Custom window fns first as those are simpler
> ways to get some of the advanced functions that timers allow for. We also
> need to be able to set and propagate the watermark correctly through the SDK
> (and validate that we do).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
