Jark Wu created FLINK-15944:
-------------------------------
Summary: Resolve the potential class conflict proplem when depend
both planners
Key: FLINK-15944
URL: https://issues.apache.org/jira/browse/FLINK-15944
Project: Flink
Issue Type: New Feature
Components: Table SQL / Legacy Planner, Table SQL / Planner
Reporter: Jark Wu
FLINK-15935 raised the potential class conflict problem when the
project/application depend old planner and blink planner at the same time.
Currently, Calcite classes (fix Calcite bugs) and
{{PlannerExpressionParserImpl}} have the same classpath and may lead to
problems when they are different.
Currently, we keep these classes in sync in both planners manually. However,
it's not safe and error-prone. We should figure out a solution for this (we
can't remove old planner in the near future).
A viable solution is having a {{flink-table-planner-common}} module to keep the
commonly used classes in both planner.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
