[
https://issues.apache.org/jira/browse/FLINK-13749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979222#comment-16979222
]
Chesnay Schepler commented on FLINK-13749:
------------------------------------------
[~aljoscha] This change implies that the client now uses child-first
classloading, correct? If so, we may want to mention that in the release notes.
> 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)
