You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Robert Metzger (JIRA)" <ji...@apache.org> on 2019/02/28 13:10:00 UTC

[jira] [Updated] (FLINK-5346) Remove all ad-hoc config loading via GlobalConfiguration

     [ https://issues.apache.org/jira/browse/FLINK-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Metzger updated FLINK-5346:
----------------------------------
    Component/s:     (was: Core)
                 Runtime / Configuration

> Remove all ad-hoc config loading via GlobalConfiguration
> --------------------------------------------------------
>
>                 Key: FLINK-5346
>                 URL: https://issues.apache.org/jira/browse/FLINK-5346
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Configuration
>            Reporter: Stephan Ewen
>            Priority: Major
>             Fix For: 2.0.0
>
>
> I think we should get rid of the static calls to {{GlobalConfiguration}} that load configuration ad hoc. It will not properly work anyways because different setups (standalone / Yarn / Mesos / etc) store and access the configuration at different places.
> The only point where the configuration should be loaded is in the entry points of the Processes (TaskManager, JobManager, ApplicationMaster, etc)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)