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

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16891702#comment-16891702 ] 

Jark Wu commented on FLINK-13267:
---------------------------------

Hi [~twalthr] [~aljoscha], I'm fine with two separate jars. 
I just renamed the title and closed this issue to unblock many other issues. 
Will create another issue to create separate uber jars. 

> 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 using different planner,  we want to package both flink planner and blink planner into an uber jar. 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)