We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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?
Imported from Jira BEAM-2061. Original Jira may contain additional context. Reported by: jgrabber.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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?
Imported from Jira BEAM-2061. Original Jira may contain additional context.
Reported by: jgrabber.
The text was updated successfully, but these errors were encountered: