You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dawid Wysakowicz (Jira)" <ji...@apache.org> on 2020/01/20 15:53:00 UTC

[jira] [Closed] (FLINK-15599) SQL client requires both legacy and blink planner to be on the classpath

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

Dawid Wysakowicz closed FLINK-15599.
------------------------------------
    Resolution: Fixed

Fixed in:
master: fd2b8e5894d43100802dfa17b7a1ea7d1e505d63
1.10: ca1cacd3494232bb7f34327c829033160a86abcd

> 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
>            Assignee: Jingsong Lee
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)