[ https://issues.apache.org/jira/browse/FLINK-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355143#comment-15355143 ]
ASF GitHub Bot commented on FLINK-4084: --------------------------------------- Github user alkagin commented on a diff in the pull request: https://github.com/apache/flink/pull/2149#discussion_r68937366 --- Diff: flink-clients/src/main/java/org/apache/flink/client/CliFrontend.java --- @@ -132,9 +132,9 @@ - private final Configuration config; + private Configuration config; --- End diff -- > Could we make the configDir parameter a general parameter that goes before run, list, cancel, etc.? Sounds good. `configDir` must be positional after `flink` or I may do something like this `flink run --configDir /my/custom/dir -p 10 /path/to/jar`? > You could parse the config parameter in the constructor and initialize the config only once. Then continue with the normal parsing. Now `configDir` is traversal on all actions, i can do it. > Add configDir parameter to CliFrontend and flink shell script > ------------------------------------------------------------- > > Key: FLINK-4084 > URL: https://issues.apache.org/jira/browse/FLINK-4084 > Project: Flink > Issue Type: Improvement > Components: Client > Affects Versions: 1.1.0 > Reporter: Till Rohrmann > Assignee: Andrea Sella > Priority: Minor > > At the moment there is no other way than the environment variable > FLINK_CONF_DIR to specify the configuration directory for the CliFrontend if > it is started via the flink shell script. In order to improve the user > exprience, I would propose to introduce a {{--configDir}} parameter which the > user can use to specify a configuration directory more easily. -- This message was sent by Atlassian JIRA (v6.3.4#6332)