beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Cwik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-2061) Hint to template job creation in DataflowRunner / DataflowPipelineOptions
Date Mon, 24 Apr 2017 15:38:04 GMT

    [ https://issues.apache.org/jira/browse/BEAM-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981375#comment-15981375
] 

Luke Cwik commented on BEAM-2061:
---------------------------------

If you would like to take on this task, feel free to assign the issue to yourself and follow
the contribution guide:
https://beam.apache.org/contribute/contribution-guide/

> 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
>            Assignee: Daniel Halperin
>            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)

Mime
View raw message