You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/10/04 17:51:00 UTC

[jira] [Work logged] (BEAM-7977) DataflowRunner writes to System.out instead of logging

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

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

                Author: ASF GitHub Bot
            Created on: 04/Oct/19 17:50
            Start Date: 04/Oct/19 17:50
    Worklog Time Spent: 10m 
      Work Description: pabloem commented on pull request #9337: [BEAM-7977] use LOG.info instead of System.out.println in DataflowRunner
URL: https://github.com/apache/beam/pull/9337
 
 
   
 
----------------------------------------------------------------
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:
users@infra.apache.org


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

    Worklog Id:     (was: 323623)
    Time Spent: 50m  (was: 40m)

> 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: 50m
>  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)