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

ASF GitHub Bot commented on BEAM-802:
-------------------------------------

GitHub user mariapython opened a pull request:

    https://github.com/apache/beam/pull/1743

    [BEAM-802] Add StaticValueProvider class for FileBasedSource I/O Transforms

    - [x] Add ValueProvider class and derive StaticValueProvider from it.
    - [x] Modify FileBasedSource I/O transforms to accept objects of type 
ValueProvider.
    - [x] Modify display_data.
    - [ ] Modify other I/O transforms.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mariapython/incubator-beam ppp_vp

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/beam/pull/1743.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 #1743
    
----
commit 95502b3e8681867f8337938b812d9db1ffaa11ed
Author: Maria Garcia Herrero <[email protected]>
Date:   2017-01-06T03:02:58Z

    Add StaticValueProvider class for FileBasedSource I/O Transforms

----


> 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.4#6332)

Reply via email to