[
https://issues.apache.org/jira/browse/BEAM-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132180#comment-17132180
]
Beam JIRA Bot commented on BEAM-101:
------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Data-driven triggers
> --------------------
>
> Key: BEAM-101
> URL: https://issues.apache.org/jira/browse/BEAM-101
> Project: Beam
> Issue Type: New Feature
> Components: beam-model
> Reporter: Robert Bradshaw
> Priority: P2
> Labels: stale-P2
>
> For some applications, it's useful to declare a pane/window to be emitted (or
> finished) based on its contents. The simplest of these is the AfterCount
> trigger, but more sophisticated predicates could be constructed.
> The requirements for consistent trigger firing are essentially that the state
> of the trigger form a lattice and that the "should fire?" question is a
> monotonic predicate on the lattice. Basically it asks "are we high enough up
> the lattice?"
> Because the element types may change between the application of Windowing and
> the actuation of the trigger, one idea is to extract the relevant data from
> the element at Windowing and pass it along implicitly where it can be
> combined and inspected in a type safe way later (similar to how timestamps
> and windows are implicitly passed with elements).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
