[jira] [Updated] (FLINK-11470) LocalEnvironment doesn't call FileSystem.initialize()

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ 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 pull-request-available stale-assigned  (was: auto-deprioritized-major auto-unassigned pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issue is assigned but has not received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a comment updating the community on your progress.  If this issue is waiting on feedback, please consider this a reminder to the committer/reviewer. Flink is a very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone else may work on it.


> 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, 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.20.1#820001)