[
https://issues.apache.org/jira/browse/FLINK-17195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089162#comment-17089162
]
Teng Fei Liao commented on FLINK-17195:
---------------------------------------
"Wrong" might not be the most correct word. At the very least, it's a
behavioral difference between the two planners. Some of the jars we're shipping
aren't owned by us so it's non-trivial to rewrite them in order to avoid this
issue.
> Worker threads for source function have wrong ClassLoader
> ---------------------------------------------------------
>
> Key: FLINK-17195
> URL: https://issues.apache.org/jira/browse/FLINK-17195
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.10.0
> Reporter: Teng Fei Liao
> Priority: Major
>
> Hey, in one of my SourceFunctions, I'm calling
> ServiceLoader.load(MyDefiniedService.class) which internally fetches the
> ClassLoader by calling Thread.currentThread().getContextClassLoader(). It
> seems like whichever ClassLoader this fetches is unaware of any jars/code
> that I've shipped.
> My application code has not changed and this came up in my attempt switch
> planners from the old planner to the blink planner. Would appreciate any help
> I can get on this, thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
