[ https://issues.apache.org/jira/browse/FLINK-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999166#comment-16999166 ]
Arvid Heise commented on FLINK-15219: ------------------------------------- Piotr suggested to provide a manual hook for users to initialize `Plugins.initialize(<dir>)` in their respective main. Then we can later support non-filesystem plugins. > LocalEnvironment is not initializing plugins > -------------------------------------------- > > Key: FLINK-15219 > URL: https://issues.apache.org/jira/browse/FLINK-15219 > Project: Flink > Issue Type: Bug > Components: Runtime / Task > Affects Versions: 1.10.0 > Reporter: Arvid Heise > Priority: Major > > Currently, plugins cannot be used in `LocalEnvironment` as `FileSystem`s are > only initialized without `PluginManager`. In all other environments, the > plugin manager is initialized in `TaskManagerRunner`. > > That means unless a user manually adds > {code:java} > final Configuration configuration = new Configuration(); > FileSystem.initialize(configuration, > PluginUtils.createPluginManagerFromRootFolder(configuration)); > {code} > to his entry point, he cannot use plugins, which means no s3 filesystems > after FLINK-11956. > We should add the proper initialization to the LocalExecutionEnvironment (at > LocalExecutor?), so that the user does not have to it manually. -- This message was sent by Atlassian Jira (v8.3.4#803005)