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

dalongliu updated FLINK-29240:
------------------------------
    Description: 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.

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

Reply via email to