You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2019/07/23 08:26:00 UTC
[jira] [Comment Edited] (FLINK-13267) Package Flink planner and
Blink planner into an uber jar
[ https://issues.apache.org/jira/browse/FLINK-13267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890774#comment-16890774 ]
Aljoscha Krettek edited comment on FLINK-13267 at 7/23/19 8:25 AM:
-------------------------------------------------------------------
Just writing to make sure that we create two separate uber jars, one for each planner. It wasn't 100% clear from the description.
was (Author: aljoscha):
Just writing to make sure that we create two separate uber jars, one for each planner.
> Package Flink planner and Blink planner into an uber jar
> --------------------------------------------------------
>
> 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)