[
https://issues.apache.org/jira/browse/FLINK-15219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-15219:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
