beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-551) Support Dynamic PipelineOptions
Date Mon, 26 Sep 2016 22:49:20 GMT

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

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

GitHub user sammcveety opened a pull request:

    https://github.com/apache/incubator-beam/pull/1009

    [BEAM-551] Add ValueProvider class (Take 2)

    My branch had become a dumpster fire, so I'm opening a fresh PR (history is here: https://github.com/apache/incubator-beam/pull/827).
    
    Add a basic implementation of StaticValueProvider and DynamicValueProvider.
    
    @dhalperi , could you please take a look?  Hoping the jackson API surface test failures
are easy to fix. 

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

    $ git pull https://github.com/sammcveety/incubator-beam sgmc/vp2

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

    https://github.com/apache/incubator-beam/pull/1009.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 #1009
    
----
commit 3e55e508ede87b92f0d78bc960803bc546a8a354
Author: sammcveety <sam.mcveety@gmail.com>
Date:   2016-09-26T22:27:15Z

    Reset of ValueProvider PR.

commit 562baf6ec7a9a77dad797c5a40df1f5122e5d1b8
Author: sammcveety <sam.mcveety@gmail.com>
Date:   2016-09-26T22:46:05Z

    Fix checkstyle, etc., failures.

----


> Support Dynamic PipelineOptions
> -------------------------------
>
>                 Key: BEAM-551
>                 URL: https://issues.apache.org/jira/browse/BEAM-551
>             Project: Beam
>          Issue Type: New Feature
>          Components: beam-model
>            Reporter: Sam McVeety
>            Assignee: Frances Perry
>            Priority: Minor
>
> During the graph construction phase, the given SDK generates an initial
> execution graph for the program.  At execution time, this graph is
> executed, either locally or by a service.  Currently, Beam only supports
> parameterization at graph construction time.  Both Flink and Spark supply
> functionality that allows a pre-compiled job to be run without SDK
> interaction with updated runtime parameters.
> In its current incarnation, Dataflow can read values of PipelineOptions at
> job submission time, but this requires the presence of an SDK to properly
> encode these values into the job.  We would like to build a common layer
> into the Beam model so that these dynamic options can be properly provided
> to jobs.
> Please see
> https://docs.google.com/document/d/1I-iIgWDYasb7ZmXbGBHdok_IK1r1YAJ90JG5Fz0_28o/edit
> for the high-level model, and
> https://docs.google.com/document/d/17I7HeNQmiIfOJi0aI70tgGMMkOSgGi8ZUH-MOnFatZ8/edit
> for
> the specific API proposal.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message