[
https://issues.apache.org/jira/browse/BEAM-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15981391#comment-15981391
]
Daniel Halperin commented on BEAM-2061:
---------------------------------------
Additionally, please refer to the Dataflow 2.0 release notes for information on
porting between Dataflow SDK for Java 1.x and 2.x:
https://cloud.google.com/dataflow/release-notes/release-notes-java-2#replaced_templatingdataflowpipelinerunner_with_--templatelocation
> 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)
