You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chalres Tan (Jira)" <ji...@apache.org> on 2023/04/18 18:39:00 UTC

[jira] [Commented] (FLINK-29240) Unify the ClassLoader in StreamExecutionEnvironment and TableEnvironment

    [ https://issues.apache.org/jira/browse/FLINK-29240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713715#comment-17713715 ] 

Chalres Tan commented on FLINK-29240:
-------------------------------------

Hi [~lsy], I was wondering if this issue will receive any attention for the next Flink release as this is the root ticket for the breaking UDF classloading functionality since Flink 1.16 (https://issues.apache.org/jira/browse/FLINK-29890). We currently are using a workaround for the issue, but it would be great if this ticket gets picked up so we can clean up the code on our end.

> Unify the ClassLoader in StreamExecutionEnvironment and TableEnvironment
> ------------------------------------------------------------------------
>
>                 Key: FLINK-29240
>                 URL: https://issues.apache.org/jira/browse/FLINK-29240
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Task, Table SQL / API
>    Affects Versions: 1.16.0
>            Reporter: dalongliu
>            Priority: Major
>             Fix For: 1.18.0
>
>
> Since [FLINK-15635| https://issues.apache.org/jira/browse/FLINK-15635], we have introduced a user classloader in table module to manage all user jars, such as the jar added by `ADD JAR` or `CREATE FUNCTION ... USING JAR` syntax. However, in table API  program user can create `StreamExecutionEnvironment` first, then create `TableEnvironment` based on it, the classloader in `StreamExecutionEnvironment` and `TableEnvironment` are not the same.  if the user use `ADD JAR` syntax in SQL query, here maybe occur ClassNotFoundException during compile StreamGraph to JobGraph because of the different classloader, so we need to unify the classloader, make sure the classloader is the same.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)