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 Tue, 27 Dec 2016 15:27:58 GMT


ASF GitHub Bot commented on BEAM-551:

GitHub user sammcveety opened a pull request:

    [BEAM-551] Cache value in NVP.get()

    My understanding is that since assignment is atomic, further concurrency handling is not
needed, but I am inexpert in Java's handling of such.
    R: @dhalperi

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

    $ git pull cache_values_in_nvp

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 #1698
commit 1af3e078da65672ad9c9e32daa4168a409693776
Author: sammcveety <>
Date:   2016-12-27T14:56:53Z


commit 811397877d6053d48b8e5442f6a9cac87873b3b4
Author: Sam McVeety <>
Date:   2016-12-27T15:10:07Z



> Support Dynamic PipelineOptions
> -------------------------------
>                 Key: BEAM-551
>                 URL:
>             Project: Beam
>          Issue Type: New Feature
>          Components: beam-model
>            Reporter: Sam McVeety
>            Assignee: Sam McVeety
>            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