[
https://issues.apache.org/jira/browse/BEAM-7977?focusedWorklogId=325893&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325893
]
ASF GitHub Bot logged work on BEAM-7977:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Oct/19 19:49
Start Date: 09/Oct/19 19:49
Worklog Time Spent: 10m
Work Description: lukecwik 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-540161257
I think we used System.out.println so that users who have incorrect logging
configuration would still get some output when they submit a job.
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 325893)
Time Spent: 1h (was: 50m)
> 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: 1h
> 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
(v8.3.4#803005)
