[jira] [Commented] (BEAM-101) Data-driven triggers

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on BEAM-101:
-------------------------------------

GitHub user katsiapis opened a pull request:

    https://github.com/apache/incubator-beam/pull/1392

    [BEAM-101] A few improvements to Apache Beam Python's FileIO.

    - Ensuring that AUTO compression works properly for FileSinks.
    - Introducing __enter__ and __exit__ in _CompressedFile to allow use
      of "with", and updating textio accordingly.

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

    $ git pull https://github.com/katsiapis/incubator-beam fileio

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

    https://github.com/apache/incubator-beam/pull/1392.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 #1392
    
----
commit 5748647aa0d409828f9769dbc472bdb50f92a343
Author: Gus Katsiapis <ka...@katsiapis-linux.mtv.corp.google.com>
Date:   2016-11-19T02:31:20Z

    A few improvements to Apache Beam Python's FileIO.
    
    - Ensuring that AUTO compression works properly for FileSinks.
    - Introducing __enter__ and __exit__ in _CompressedFile to allow use
      of "with", and updating textio accordingly.

----


> 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
>            Assignee: Frances Perry
>
> 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
(v6.3.4#6332)