[
https://issues.apache.org/jira/browse/FLINK-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154009#comment-15154009
]
Aljoscha Krettek commented on FLINK-3399:
-----------------------------------------
Unfortunately I did not yet have time to look into this because we are very
busy with the 1.0 release right now. At a very hight level, I think it requires
that we internally keep some kind of tree of how compound triggers relate to
each other (are nested) and also information about which triggers are finished.
Also we need to figure out what happens if two triggers of a compound OrTrigger
fire and they have differing TriggerResults, for example one says PURGE, the
other says FIRE.
Once the release is out I'll have more time too think about this. But if you're
interested you can also make some investigations and try to figure out what
would be required. AFAIK Apache Beam (Google Cloud Dataflow) has a very
sophisticated system for triggers, maybe you could have a look at that one and
try to find out what can be learned from them.
> Count with timeout trigger
> --------------------------
>
> Key: FLINK-3399
> URL: https://issues.apache.org/jira/browse/FLINK-3399
> Project: Flink
> Issue Type: Improvement
> Reporter: Shikhar Bhushan
> Priority: Minor
>
> I created an implementation of a trigger that I'd like to contribute,
> https://gist.github.com/shikhar/2cb9f1b792be31b7c16e
> An example application - if a sink function operates more efficiently if it
> is writing in a batched fashion, then the windowing mechanism + this trigger
> can be used. Count to have an upper bound on batch size & better control on
> memory usage, and timeout to ensure timeliness of the outputs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
