You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2019/07/29 08:22:00 UTC

[jira] [Reopened] (FLINK-13267) Making it possible to have both flink planner and blink planner in classpath

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

Timo Walther reopened FLINK-13267:
----------------------------------

I will reopen this issue because two subtasks are still open.

> Making it possible to have both flink planner and blink planner in classpath
> ----------------------------------------------------------------------------
>
>                 Key: FLINK-13267
>                 URL: https://issues.apache.org/jira/browse/FLINK-13267
>             Project: Flink
>          Issue Type: Task
>          Components: Table SQL / Planner
>    Affects Versions: 1.9.0
>            Reporter: Jark Wu
>            Assignee: Jark Wu
>            Priority: Blocker
>             Fix For: 1.9.0, 1.10.0
>
>
> In order to have a good experience for users when switching different planners,  we want to have both flink planner and blink planner in one classpath. So that, users can not care about cluster setup when changing planner.
> This is an umbrella issue to track all the problems need to fix before this can happen. A detailed problems is listed in the google doc: https://docs.google.com/document/d/15Z1Khy23DwDBp956yBzkMYkGdoQAU_QgBoJmFWSffow/edit#



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)