flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hequn Cheng (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-13749) Make Flink client respect classloading policy
Date Wed, 29 Jan 2020 03:29:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-13749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Hequn Cheng updated FLINK-13749:
    Fix Version/s:     (was: 1.9.2)
                       (was: 1.8.3)

> Make Flink client respect classloading policy
> ---------------------------------------------
>                 Key: FLINK-13749
>                 URL: https://issues.apache.org/jira/browse/FLINK-13749
>             Project: Flink
>          Issue Type: Bug
>          Components: Command Line Client, Runtime / REST
>            Reporter: Paul Lin
>            Assignee: Paul Lin
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.10.0
>          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

View raw message