You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2017/04/06 19:28:41 UTC

[jira] [Closed] (FLINK-4644) Deprecate "flink.base.dir.path" from ConfigConstants

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

Chesnay Schepler closed FLINK-4644.
-----------------------------------
       Resolution: Fixed
         Assignee: Stephan Ewen  (was: Maximilian Michels)
    Fix Version/s: 1.3.0

Fixed in 8780cb6c4fa05f7cd6167f1240d03f407d8d41ea.

> Deprecate "flink.base.dir.path" from ConfigConstants
> ----------------------------------------------------
>
>                 Key: FLINK-4644
>                 URL: https://issues.apache.org/jira/browse/FLINK-4644
>             Project: Flink
>          Issue Type: Wish
>          Components: Build System
>    Affects Versions: 1.2.0
>            Reporter: Maximilian Michels
>            Assignee: Stephan Ewen
>            Priority: Minor
>             Fix For: 1.3.0
>
>
> Flink's configuration entry "flink.base.dir.path" is not documented anywhere but present in {{ConfigConstants}}. It is set in the JobManager but it is not accessed anywhere in the code.
> I propose to deprecate the entry from ConfigConstants:
> public static final String FLINK_BASE_DIR_PATH_KEY = "flink.base.dir.path";
> I think this entry can only possibly be abused by users to write into the Flink base dir or rely on some structure of the directory (which is different for standalone, yarn/mesos). The only way i can see such a variable being useful if it is present in the form of an environment variable to make it available to other systems.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)