beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-551) Support Dynamic PipelineOptions
Date Thu, 20 Oct 2016 16:42:59 GMT


ASF GitHub Bot commented on BEAM-551:

GitHub user sammcveety opened a pull request:

    [BEAM-551] Add NestedValueProvider

    Wrote this up based on some nascent thoughts, and looking ahead to PubsubIO, which uses
a bunch of wrapper classes instead of String.  This allows us to nicely turn those into VP<WrapperClass>
instead of deferring all the translation code into the caller, which would be gross.
    R: @dhalperi 

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

    $ git pull sgmc/nested_vp

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

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1146
commit e06fd8ce238971d1b235ce01f527f7cedb058127
Author: sammcveety <>
Date:   2016-10-20T16:29:04Z

    Add NestedValueProvider


> Support Dynamic PipelineOptions
> -------------------------------
>                 Key: BEAM-551
>                 URL:
>             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
> for the high-level model, and
> for
> the specific API proposal.

This message was sent by Atlassian JIRA

View raw message