[
https://issues.apache.org/jira/browse/FLINK-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885754#comment-16885754
]
Jark Wu commented on FLINK-13266:
---------------------------------
Hi [~twalthr], I think it's a good idea. However, the {{flink.table.planner}}
and {{flink.table.runtime}} have already been used for some purpose.
{{flink.table.planner}} is used for {{Planner}} relative classes. And
{{flink.table.runtime}} is used for runtime operators. And we have some other
packages which maybe not appropriate to put them in {{flink.table.planner}} or
{{flink.table.runtime}}, for example, {{flink.table.executor}},
{{flink.table.catalog}}, {{flink.table.codegen}}.
> 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)
