You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Daniel Halperin (JIRA)" <ji...@apache.org> on 2017/04/25 15:53:04 UTC

[jira] [Assigned] (BEAM-2061) Hint to template job creation in DataflowRunner / DataflowPipelineOptions

     [ https://issues.apache.org/jira/browse/BEAM-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Halperin reassigned BEAM-2061:
-------------------------------------

    Assignee:     (was: Daniel Halperin)

> Hint to template job creation in DataflowRunner / DataflowPipelineOptions 
> --------------------------------------------------------------------------
>
>                 Key: BEAM-2061
>                 URL: https://issues.apache.org/jira/browse/BEAM-2061
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow
>    Affects Versions: 0.6.0
>            Reporter: Jonas Grabber
>            Priority: Trivial
>              Labels: documentation
>
> Hello,
> the SDK documentation for both DataflowPipelineOptions and DataflowRunner "fail" to mention the ability to create template jobs in Google Dataflow.
> Especially with the loss of the separate DataflowTemplateRunner this caused confusion amongst my working colleagues and other Beam users I talked to.
> A short hit to the setTemplateLocation method would save a decent amount of time across a lot of developers, I reckon.
> What's the procedure for these kind of (cosmetic) issues?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)