[
https://issues.apache.org/jira/browse/FLINK-11470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-11470:
-----------------------------------
Labels: auto-deprioritized-major auto-unassigned (was: auto-unassigned
stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> LocalEnvironment doesn't call FileSystem.initialize()
> -----------------------------------------------------
>
> Key: FLINK-11470
> URL: https://issues.apache.org/jira/browse/FLINK-11470
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
> Affects Versions: 1.6.2
> Reporter: Nico Kruber
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned
>
> Proper Flink cluster components, e.g. task manager or job manager, initialize
> configured file systems with their parsed {{Configuration}} objects. However,
> the {{LocalEnvironment}} does not seem to do that and we therefore lack the
> ability to configure access credentials etc like in the following example:
> {code}
> Configuration config = new Configuration();
> config.setString("s3.access-key", "user");
> config.setString("s3.secret-key", "secret");
> // FileSystem.initialize(config);
> final ExecutionEnvironment exEnv =
> ExecutionEnvironment.createLocalEnvironment(config);
> {code}
> The workaround is to call {{FileSystem.initialize(config);}} yourself but it
> is actually surprising that this is not done automatically.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
