You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Davor Bonaci (JIRA)" <ji...@apache.org> on 2017/08/24 21:03:01 UTC

[jira] [Commented] (BEAM-1691) Dynamic properties supported in PipelineOptions

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

Davor Bonaci commented on BEAM-1691:
------------------------------------

I'd resolve for now; if we want to change the behavior here, perhaps there should be a dev@ discussion first.

> Dynamic properties supported in PipelineOptions
> -----------------------------------------------
>
>                 Key: BEAM-1691
>                 URL: https://issues.apache.org/jira/browse/BEAM-1691
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Xu Mingmin
>            Assignee: Davor Bonaci
>             Fix For: Not applicable
>
>
> Usually the two lines to create a new Beam pipeline are:
> {code}
> Options options = PipelineOptionsFactory.fromArgs(args).withValidation().as(Options.class);
> Pipeline pipeline = Pipeline.create(options);
> {code} 
> As each runner has its own PipelineOptions, one piece of code is hardly to run on different runners without code change, --as least Options needs to be updated.
> Dynamic property could be a choice, similar as
> {code}
> -D property1=value1 -D property2=value2 ...
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)