Re: [jira] [Closed] (BEAM-178) stdout vs logging in DataflowPipelineRunner?

[Lukasz Cwik <lc...@google.com.INVALID>]

Yes, what Dan said that I said.

On Mon, Apr 11, 2016 at 9:48 AM, Davor Bonaci (JIRA) <ji...@apache.org>
wrote:

>
>      [
> https://issues.apache.org/jira/browse/BEAM-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Davor Bonaci closed BEAM-178.
> -----------------------------
>     Resolution: Not A Bug
>
> > stdout vs logging in DataflowPipelineRunner?
> > --------------------------------------------
> >
> >                 Key: BEAM-178
> >                 URL: https://issues.apache.org/jira/browse/BEAM-178
> >             Project: Beam
> >          Issue Type: Bug
> >          Components: runner-dataflow
> >            Reporter: Daniel Halperin
> >            Assignee: Davor Bonaci
> >            Priority: Minor
> >
> > We seem to thoroughly intermingle logging and println. Is this
> deliberate?
> > e.g.,
> > {code}
> >     LOG.info("To access the Dataflow monitoring console, please navigate
> to {}",
> >         MonitoringUtil.getJobMonitoringPageURL(options.getProject(),
> jobResult.getId()));
> >     System.out.println("Submitted job: " + jobResult.getId());
> > {code}
> > Original genesis for this was noticing a println in a backport Cl:
> https://github.com/apache/incubator-beam/blob/master/sdks/java/core/src/main/java/com/google/cloud/dataflow/sdk/runners/DataflowPipelineRunner.java#L451
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
>