[ 
https://issues.apache.org/jira/browse/BEAM-7977?focusedWorklogId=294692&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-294692
 ]

ASF GitHub Bot logged work on BEAM-7977:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Aug/19 11:16
            Start Date: 14/Aug/19 11:16
    Worklog Time Spent: 10m 
      Work Description: sgrj commented on issue #9337: [BEAM-7977] use LOG.info 
instead of System.out.println in DataflowRunner
URL: https://github.com/apache/beam/pull/9337#issuecomment-521204710
 
 
   I did a quick grep for other instances of System.out and System.err. They 
all seem to be in tests, examples, or command line apps, which seem like valid 
usages. The only other instance that might be changed is 
https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/src/main/java/org/apache/beam/runners/dataflow/DataflowRunner.java#L700;
 but since that seems to be used for debugging only, writing to stdout seems to 
be ok here as well.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 294692)
    Time Spent: 20m  (was: 10m)

> DataflowRunner writes to System.out instead of logging
> ------------------------------------------------------
>
>                 Key: BEAM-7977
>                 URL: https://issues.apache.org/jira/browse/BEAM-7977
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Sebastian Jambor
>            Assignee: Sebastian Jambor
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> DataflowRunner writes two lines to stdout for every job, which bypasses the 
> logger setup. This is slightly annoying, especially if many jobs are started 
> programmatically.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to