[
https://issues.apache.org/jira/browse/BEAM-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Burke updated BEAM-3304:
-------------------------------
Description:
Add support for triggers.
Triggers are special runner side behavior indicating how to handle data WRT the
watermark and window. Commonly configuring the processing for “late data” and
similar.
These are not currently implemented for user use in the Go SDK. Reshuffle
configures triggers, but it’s not accessible. A correct trigger implementation
can at least re-implement Reshuffle in a user pipeline, rather than handled
specially within the framework.
* Requires extending the window package to be able to configure the various
triggers.
* Specifically being able to compose triggers as also permitted by the proto.
* Requires updating the graphx package translate.go to marshal (and
unmarshal?) the triggers to and from Beam PipelineProto Windowing strategies.
* Requires supporting triggers with the beam.WindowInto transform for user
pipeline use.
**
[https://github.com/apache/beam/blob/6e7b1c44bc7275ee047afc059fd610cd3f4e5bee/sdks/go/pkg/beam/windowing.go]
* Extension: Handle pane propagation and observation in the exec package, and
in user dofns.
* Panes indicate whether data was on time or not, and similar facets.
* Might simply extend the existing window interface.
Similar to windowing, many of the same places as
https://issues.apache.org/jira/browse/BEAM-11100 need to be modified.
At simplest though, it's mostly a runner side construction, with less concern
on the exec side, and generally much simpler.
Appropriate integration tests against portable runners must be implemented, and
was:
Add support for triggers.
Triggers are special runner side behavior indicating how to handle data WRT the
watermark and window. Commonly configuring the processing for “late data” and
similar.
These are not currently implemented for user use in the Go SDK. Reshuffle
configures triggers, but it’s not accessible. A correct trigger implementation
can at least re-implement Reshuffle in a user pipeline, rather than handled
specially within the framework.
* Requires extending the window package to be able to configure the various
triggers.
* Specifically being able to compose triggers as also permitted by the proto.
* Requires updating the graphx package translate.go to marshal (and
unmarshal?) the triggers to and from Beam PipelineProto Windowing strategies.
* Requires supporting triggers with the beam.WindowInto transform for user
pipeline use.
**
[https://github.com/apache/beam/blob/6e7b1c44bc7275ee047afc059fd610cd3f4e5bee/sdks/go/pkg/beam/windowing.go]
* Extension: Handle pane propagation and observation in the exec package, and
in user dofns.
* Panes indicate whether data was on time or not, and similar facets.
* Might simply extend the existing window interface.
> Go triggering support
> ---------------------
>
> Key: BEAM-3304
> URL: https://issues.apache.org/jira/browse/BEAM-3304
> Project: Beam
> Issue Type: Improvement
> Components: sdk-go
> Reporter: Henning Rohde
> Priority: P3
>
> Add support for triggers.
> Triggers are special runner side behavior indicating how to handle data WRT
> the watermark and window. Commonly configuring the processing for “late data”
> and similar.
> These are not currently implemented for user use in the Go SDK. Reshuffle
> configures triggers, but it’s not accessible. A correct trigger
> implementation can at least re-implement Reshuffle in a user pipeline, rather
> than handled specially within the framework.
> * Requires extending the window package to be able to configure the various
> triggers.
> * Specifically being able to compose triggers as also permitted by the proto.
> * Requires updating the graphx package translate.go to marshal (and
> unmarshal?) the triggers to and from Beam PipelineProto Windowing strategies.
> * Requires supporting triggers with the beam.WindowInto transform for user
> pipeline use.
> **
> [https://github.com/apache/beam/blob/6e7b1c44bc7275ee047afc059fd610cd3f4e5bee/sdks/go/pkg/beam/windowing.go]
>
> * Extension: Handle pane propagation and observation in the exec package,
> and in user dofns.
> * Panes indicate whether data was on time or not, and similar facets.
> * Might simply extend the existing window interface.
>
> Similar to windowing, many of the same places as
> https://issues.apache.org/jira/browse/BEAM-11100 need to be modified.
> At simplest though, it's mostly a runner side construction, with less concern
> on the exec side, and generally much simpler.
> Appropriate integration tests against portable runners must be implemented,
> and
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
