[
https://issues.apache.org/jira/browse/FLINK-15599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016806#comment-17016806
]
Dawid Wysakowicz commented on FLINK-15599:
------------------------------------------
One more dependency I found is that we check explicitly for an instance of
Blink's executor in
{{org.apache.flink.table.client.gateway.local.ExecutionContext#createPipeline(java.lang.String,
org.apache.flink.configuration.Configuration)}}. This also might be
problematic.
I will assign this issue to you.
> SQL client requires both legacy and blink planner to be on the classpath
> ------------------------------------------------------------------------
>
> Key: FLINK-15599
> URL: https://issues.apache.org/jira/browse/FLINK-15599
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Client
> Affects Versions: 1.10.0
> Reporter: Dawid Wysakowicz
> Priority: Critical
> Fix For: 1.10.0
>
>
> Sql client uses directly some of the internal classes of the legacy planner,
> thus it does not work with only the blink planner on the classpath.
> The internal class that's being used is
> {{org.apache.flink.table.functions.FunctionService}}
> This dependency was introduced in FLINK-13195
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
