[
https://issues.apache.org/jira/browse/FLINK-13749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aljoscha Krettek closed FLINK-13749.
------------------------------------
Release Note:
The Flink client now also respects the configured classloading policy, i.e.
parent-first or child-first classloading. Previously only cluster components
such as the job manager or task manager supported this setting.
This does mean that users might get different behaviour in their programs, in
which case they should configure the classloading policy explicity to use
parent-first classloading, which was the previous (hard-coded) behaviour.
Resolution: Fixed
> Make Flink client respect classloading policy
> ---------------------------------------------
>
> Key: FLINK-13749
> URL: https://issues.apache.org/jira/browse/FLINK-13749
> Project: Flink
> Issue Type: Improvement
> Components: Command Line Client, Runtime / REST
> Reporter: Paul Lin
> Assignee: Paul Lin
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.10.0, 1.8.3, 1.9.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, Flink client does not respect the classloading policy and uses
> hardcoded parent-first classloader, while the other components like
> jobmanager and taskmanager use child-first classloader by default and respect
> the classloading options. This makes the client more likely to have
> dependency conflicts, especially after we removed the convenient hadoop
> binaries (so users need to add hadoop classpath in the client classpath).
> So I propose to make Flink client's (including cli and rest handler)
> classloading behavior aligned with the other components.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
