You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/02/15 05:45:18 UTC

[jira] [Commented] (FLINK-3399) Count with timeout trigger

    [ https://issues.apache.org/jira/browse/FLINK-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15146900#comment-15146900 ] 

ASF GitHub Bot commented on FLINK-3399:
---------------------------------------

GitHub user shikhar opened a pull request:

    https://github.com/apache/flink/pull/1636

    [FLINK-3399] CountWithTimeoutTrigger

    trigger that fires once the number of elements in a pane reaches the given count or the timeout expires, whichever happens first

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shikhar/flink count-with-timeout-trigger

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/1636.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1636
    
----
commit 72d8c902d42d0709cdf27897ea75dab826fe1aa4
Author: shikhar <sh...@schmizz.net>
Date:   2016-02-15T04:38:50Z

    [FLINK-3399] CountWithTimeoutTrigger

----


> 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)