[
https://issues.apache.org/jira/browse/FLINK-14991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321432#comment-17321432
]
Flink Jira Bot commented on FLINK-14991:
----------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> Export `FLINK_HOME` environment variable to all the entrypoint
> --------------------------------------------------------------
>
> Key: FLINK-14991
> URL: https://issues.apache.org/jira/browse/FLINK-14991
> Project: Flink
> Issue Type: Improvement
> Components: Command Line Client, Deployment / Scripts
> Reporter: Guowei Ma
> Priority: Minor
> Labels: stale-minor
>
> Currently, Flink depends on 6 types of files: configuration files, system
> jars files, script files、library jar files, plugin jar files, and user jars
> files. These files are in different directories.
> Flink exports 5 environment variables to locate these different type files:
> `FLINK_CONF_DIR`,`FLINK_LIB_DIR`,`FLINK_OPT_DIR`,`FLINK_PLUGIN_DIR`,`FLINK_BIN_DIR`.
> It is not a good style that exports an environment variable for every type of
> file.
> So this jira proposes to export the `FLINK_HOME` environment variable to all
> the entrypoint. Derive the directory of the different type files from the
> `FLINK_HOME` environment variable and every type file has a fixed directory
> name.
> This also has another benefit that the method implies the directory
> structure is the same in all the situations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
