You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2023/03/23 08:52:15 UTC

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

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

Xintong Song updated FLINK-29240:
---------------------------------
    Fix Version/s: 1.18.0
                       (was: 1.17.0)

> 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)