beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-23) User-facing state and timers for ParDo(DoFn)
Date Thu, 17 Nov 2016 19:13:58 GMT

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

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

GitHub user kennknowles opened a pull request:

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

    [BEAM-23] DirectRunner: rewrite single-output ParDo to multi-output

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
    
     - [x] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt).
    
    ---
    
    This is in service of simplifying the override and expansion for splittable and stateful
`ParDo`.


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

    $ git pull https://github.com/kennknowles/incubator-beam direct-ParDoSingleViaMulti

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

    https://github.com/apache/incubator-beam/pull/1378.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 #1378
    
----
commit 0b7fcc8ede9d16d02d047f40f669606cbe00fc4e
Author: Kenneth Knowles <klk@google.com>
Date:   2016-11-17T18:14:07Z

    Separate ParDoTest cases and make them more flexible
    
    A number of excessively rigid name tests preclude runner expansion
    of ParDo. This change makes them into independent unit tests
    for better signal and makes them more accurate to the intent - the
    name should have the relevant information, but may have other
    content.

commit efe582f0fbd4d2693867e5d3d3b3db21de16a9fa
Author: Kenneth Knowles <klk@google.com>
Date:   2016-11-17T18:56:36Z

    No longer execute OldDoFnTest with DirectRunner

commit 60cb48479ee5b0b6f50100bf2f6edec3fa7a552f
Author: Kenneth Knowles <klk@google.com>
Date:   2016-11-16T23:43:47Z

    DirectRunner: Expand ParDo.Bound into ParDo.BoundMulti

commit abc19d5a4672aa0f1334b674c91196c77bf07641
Author: Kenneth Knowles <klk@google.com>
Date:   2016-11-17T19:07:32Z

    Do not override type descriptor in WithTimestamps

commit ef700c967e8589b54053bc6b5e4743f50e43ec87
Author: Kenneth Knowles <klk@google.com>
Date:   2016-11-17T19:08:48Z

    Use getNewFn for coder inferences in ParDo

----


> User-facing state and timers for ParDo(DoFn)
> --------------------------------------------
>
>                 Key: BEAM-23
>                 URL: https://issues.apache.org/jira/browse/BEAM-23
>             Project: Beam
>          Issue Type: New Feature
>          Components: beam-model
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>              Labels: State
>
> To a key-partitioned ParDo, add the ability for a user's DoFn to, on a per-key-and-window
basis:
>  - read and write consistent state
>  - set a timer to request a callback at a particular moment (in any time domain)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message