New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FLINK-3776] Flink Scala shell does not allow to set configuration fo… #1945
Conversation
…r local execution
Thanks for the pull request. Looks good. Have you tested that the configuration is loaded correctly? |
Yes, I tested it by simply assigning a non-existent directory to taskmanager.tmp.dirs in $FLINK_CONF_DIR/flink-conf.yaml which is read and parsed by GlobalConfiguration.loadConfiguration(). I got the following error messages: The above error implies that the modification to $FLINK_CONF_DIR/flink-conf.yaml is loaded correctly :-) |
Looks good. Do you think we could make this more explicit by passing the loaded configuration object to the |
Seems fine but it seems to go against the design of |
Your code works, I'll will just open a follow-up issue to make GlobalConfiguration more explicit, i.e. fail on |
Okay, I got the idea. |
Thanks for the PR! |
…r local execution This closes apache#1945 [FLINK-3655] Multiple Directories (Paths) for FileInputFormat. Removed Guava. [FLINK-3655] Multiple Directories (Paths) for FileInputFormat. Removed Guava. [FLINK-3655] Multiple Directories (Paths) for FileInputFormat. Removed Guava. [FLINK-3655] Multiple Directories (Paths) for FileInputFormat. Removed Guava. [FLINK-3655] Multiple Directories (Paths) for FileInputFormat. Removed Guava.
…r local execution This closes apache#1945
…r local execution This closes apache#1945
The current version of FlinkShell creates a new Configuration object when creating a LocalFlinkMiniCluster in FlinkShell.fetchConnectionInfo().
Instead of creating a new one, FlinkShell just needs to get a configuration object which was already created when GlobalConfiguration.loadConfiguration() is called (which is before FlinkShell.fetchConnectionInfo() is called).
Therefore, just one line modification figures out this issue as shown in this pull request.