[
https://issues.apache.org/jira/browse/FLINK-26603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779298#comment-17779298
]
Xin Chen commented on FLINK-26603:
----------------------------------
Hi, [~luoyuxia] Thank you. Yes, as the table-planner-loader module was
introduced to decouple scala, I have no specific requirements for the scala
version, so I am considering fully using the table-planner to replace
table-planner-loader for all scenarios which include scenes that do not involve
the hive dialect. Please allow me to confirm again: What I am concerned about
is the impact or risk of completely using this module on other functions or
performance when it not involves the hive dialect. I think it's also completely
okay, after all, the table-planner-loader module actually uses the
table-planner. The only difference may be that the classloader mechanism of
the loader module is no longer used? Is there any problem with this？I think
it's probably not
> [Umbrella] Decouple Hive with Flink planner
> -------------------------------------------
>
> Key: FLINK-26603
> URL: https://issues.apache.org/jira/browse/FLINK-26603
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Hive, Table SQL / Planner
> Reporter: luoyuxia
> Assignee: luoyuxia
> Priority: Major
> Fix For: 1.18.0
>
>
> To support Hive dialect with Flink, we have implemented FLIP-123, FLIP-152.
> But it also brings much maintenance burden and complexity for it mixes some
> logic specific to Hive with Flink planner. We should remove such logic from
> Flink planner and make it totally decouple with Flink planner.
> With this ticket, we expect:
> 1: there won't be any specific logic to Hive in planner module
> 2: remove flink-sql-parser-hive from flink-table module
> 3: remove the planner dependency in flink-connector-hive
> I'll update more details after investigation.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
