beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1887) Switch ParDo execution to use new DoFn in Apex runner
Date Thu, 06 Apr 2017 02:19:42 GMT


ASF GitHub Bot commented on BEAM-1887:

GitHub user tweise opened a pull request:

    [BEAM-1887] Switch Apex ParDo to new DoFn.

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] 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](
    R: @kennknowles @jkff 

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

    $ git pull BEAM-1887_Apex-NewDoFn

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

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

    This closes #2450
commit 629887cb124134cdae06087cb5159efa834df0b9
Author: Thomas Weise <>
Date:   2017-04-04T07:33:35Z

    BEAM-1887 Switch Apex ParDo to new DoFn.


> Switch ParDo execution to use new DoFn in Apex runner
> -----------------------------------------------------
>                 Key: BEAM-1887
>                 URL:
>             Project: Beam
>          Issue Type: Task
>          Components: runner-apex
>            Reporter: Thomas Weise
>            Assignee: Thomas Weise
> The Apex operator is still using OldDoFn and that needs to change to support splittable
fn, state and timers.

This message was sent by Atlassian JIRA

View raw message