You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/10/27 14:30:00 UTC
[jira] [Updated] (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 ]
ASF GitHub Bot updated FLINK-11470:
-----------------------------------
Labels: auto-deprioritized-major auto-unassigned pull-request-available (was: auto-deprioritized-major auto-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: Fabian Paul
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned, pull-request-available
>
> 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)