[
https://issues.apache.org/jira/browse/FLINK-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886673#comment-16886673
]
godfrey he edited comment on FLINK-13266 at 7/17/19 4:36 AM:
-------------------------------------------------------------
hi [~twalthr], [~jark] I have listed the changes in
https://docs.google.com/document/d/15Z1Khy23DwDBp956yBzkMYkGdoQAU_QgBoJmFWSffow
(at the end of the document), and look forward your feedback, thanks
was (Author: godfreyhe):
hi [~twalthr], [~jark] I have list the changes in
https://docs.google.com/document/d/15Z1Khy23DwDBp956yBzkMYkGdoQAU_QgBoJmFWSffow,
and look forward your feedback, thanks
> Relocate blink planner classes to avoid class clashes
> -----------------------------------------------------
>
> Key: FLINK-13266
> URL: https://issues.apache.org/jira/browse/FLINK-13266
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Affects Versions: 1.9.0
> Reporter: Jark Wu
> Assignee: Jark Wu
> Priority: Blocker
> Fix For: 1.9.0
>
>
> We should have a list to relocate classes in {{flink-table-planner-blink}}
> and {{flink-table-runtime-blink}} to avoid class clashes to make both
> planners available in a lib directory.
> Note that, not all the classes can/should be relocated. For examples: calcite
> classes, {{PlannerExpressionParserImpl}} and so on.
> The relocation package name is up to discussion. A dedicated path is
> {{org.apache.flink.table.blink}}.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
