[
https://issues.apache.org/jira/browse/FLINK-5253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075050#comment-16075050
]
ASF GitHub Bot commented on FLINK-5253:
---------------------------------------
Github user EronWright commented on the issue:
https://github.com/apache/flink/pull/3356
@tillrohrmann the `dynamicProperties` static field is unfortunate, yes.
To eliminate it, we must evaluate the use of the zero-arg
`GlobalConfiguration.loadConfiguration()` that is used in many places
(`FileInputFormat`, `HadoopUtils`). The field ensures that all those sites
see the same configuration.
> Remove special treatment of "dynamic properties"
> ------------------------------------------------
>
> Key: FLINK-5253
> URL: https://issues.apache.org/jira/browse/FLINK-5253
> Project: Flink
> Issue Type: Sub-task
> Components: YARN
> Environment: {{flip-6}} feature branch
> Reporter: Stephan Ewen
> Labels: flip-6
>
> The YARN client accepts configuration keys as command line parameters.
> Currently these are send to the AppMaster and TaskManager as "dynamic
> properties", encoded in a special way via environment variables.
> The mechanism is quite fragile. We should simplify it:
> - The YARN client takes the local {{flink-conf.yaml}} as the base.
> - It overwrite config entries with command line properties when preparing
> the configuration to be shipped to YARN container processes (JM / TM)
> - No additional handling neccessary
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
