[
https://issues.apache.org/jira/browse/BEAM-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15962044#comment-15962044
]
ASF GitHub Bot commented on BEAM-802:
-------------------------------------
GitHub user mariapython opened a pull request:
https://github.com/apache/beam/pull/2475
[BEAM-802] Skip query metrics for template creation
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
- [ ] Make sure the PR title is formatted like:
`[BEAM-<Jira issue #>] Description of pull request`
- [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
- [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
number, if there is one.
- [ ] If this contribution is large, please file an Apache
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf).
---
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mariapython/incubator-beam ppp_fix_equal
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2475.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2475
----
commit d4cddc83b04ae87b18be16795f4a9bc069f39050
Author: Maria Garcia Herrero <[email protected]>
Date: 2017-04-09T06:08:44Z
Skip query metrics when creating a template
----
> Support Dynamic PipelineOptions for python
> ------------------------------------------
>
> Key: BEAM-802
> URL: https://issues.apache.org/jira/browse/BEAM-802
> Project: Beam
> Issue Type: New Feature
> Components: sdk-py
> Reporter: María GH
> Assignee: María GH
> Priority: Minor
> Original Estimate: 1,680h
> Remaining Estimate: 1,680h
>
> Goal: Enable users to run pipelines from templates filled via CL (pipeline
> options)
> Background: Currently, the Runner creates the JSON pipeline description which
> can be sent to the worker as is, since everything is already defined there
> (with links to gs:// for input and binaries). With the parametrized approach,
> those descriptions are empty and filled by the user or defaulted, so the
> pipeline needs to be stored somewhere first until the values become available.
> Tasks:
> 1- Create template-style pipeline description (TemplateRunner)
> The graph description is now a template (some parts are not filled) that
> needs to be saved.
> 2- Define values to inject to the template (ValueProviders API)
> The placeholders can be filled with default values (static) or with dynamic
> key/value pairs provided at runtime (dynamic)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
