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-327) Dataflow runner should have configuration for System.out/err handling
Date Tue, 14 Jun 2016 16:45:57 GMT


ASF GitHub Bot commented on BEAM-327:

GitHub user swegner opened a pull request:

    [BEAM-327] Update DataflowPipelineRunner worker container version

    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](

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

    $ git pull worker-container

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 #459


> Dataflow runner should have configuration for System.out/err handling
> ---------------------------------------------------------------------
>                 Key: BEAM-327
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Scott Wegner
>            Assignee: Scott Wegner
> We would like to support the following scenarios:
> # Respect global logging filter configuration for System.out/System.err log messages.
> # Suppress all log message for a given source, including System.out/err (Level.OFF)
> # Set the log level for messages emitted from System.out/err.

This message was sent by Atlassian JIRA

View raw message