[
https://issues.apache.org/jira/browse/FLINK-11470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323379#comment-17323379
]
Flink Jira Bot commented on FLINK-11470:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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
> Assignee: vinoyang
> Priority: Major
> Labels: stale-assigned
>
> 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)
