[
https://issues.apache.org/jira/browse/FLINK-13267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891654#comment-16891654
]
Aljoscha Krettek commented on FLINK-13267:
------------------------------------------
I don't think that's the way to go: a) this makes it impossible to only add one
runner, which some people might want to do, b) the legacy Flink Runner will go
away at some point in the future, c) it's more complicated to package
everything into one jar, from a maven/build infrastructure perspective.
I think it's more work for us to package it into one jar and there's no benefit
for users, rather it makes it impossible for users to only have one runner in
the classpath if they want that.
> 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)
