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-980) Ability to configure the DAG created by Apex Runner
Date Thu, 26 Jan 2017 06:25:24 GMT


ASF GitHub Bot commented on BEAM-980:

GitHub user tweise opened a pull request:

    [BEAM-980] Support configuration of Apex DAG through properties file.

    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 

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

    $ git pull BEAM-980

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 #1850
commit 02bbf4357fe1e10c8646d4101a721721d400e997
Author: Thomas Weise <>
Date:   2017-01-26T06:22:36Z

    BEAM-980 Support configuration of Apex DAG through properties file.


> Ability to configure the DAG created by Apex Runner
> ---------------------------------------------------
>                 Key: BEAM-980
>                 URL:
>             Project: Beam
>          Issue Type: Task
>          Components: runner-apex
>            Reporter: Thomas Weise
>            Assignee: Thomas Weise
> The Beam pipeline is translated to an Apex DAG of operators that have names that are
derived from the transforms. In case of composite transforms those look like path names. Apex
lets the user configure things like memory, vcores, parallelism through properties/attributes
that reference the operator names. The configuration approach needs to be documented and supplemented
with an example.

This message was sent by Atlassian JIRA

View raw message