You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "vinoyang (JIRA)" <ji...@apache.org> on 2019/01/31 01:41:00 UTC
[jira] [Assigned] (FLINK-11470) LocalEnvironment doesn't call
FileSystem.initialize()
[ https://issues.apache.org/jira/browse/FLINK-11470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
vinoyang reassigned FLINK-11470:
--------------------------------
Assignee: vinoyang
> LocalEnvironment doesn't call FileSystem.initialize()
> -----------------------------------------------------
>
> Key: FLINK-11470
> URL: https://issues.apache.org/jira/browse/FLINK-11470
> Project: Flink
> Issue Type: Bug
> Components: Local Runtime
> Affects Versions: 1.6.2
> Reporter: Nico Kruber
> Assignee: vinoyang
> Priority: Major
>
> 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
(v7.6.3#76005)