[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
