[
https://issues.apache.org/jira/browse/FLINK-26603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17779056#comment-17779056
]
luoyuxia edited comment on FLINK-26603 at 10/24/23 12:26 PM:
-------------------------------------------------------------
[~xinchen147] Thanks for reach me out. Unfortunately, it's not a easy work to
cherry pick the feature . It still need some otherworks(the all subtask in this
umbrella issue) before you can cherry pick FLINK-31409.
If you don't care out scala-version, I don't think there's any risk that use
flink-table-planner directly. As for as I know, some users/companies did use
flink-table-planner direclty to use hive dialect, and it works well.
was (Author: luoyuxia):
[~xinchen147] Thanks for reach me out. Unfortunately, it's not a easy work to
cherry pick the feature . It still need some otherworks(the all subtask in this
umbrella issue) before you can cherry pick FLINK-31409.
If you don't care out scala-version, I don't think there's any risk that use
flink-table-planner directly. As for as I know, some users/companies do like
your to use hive dialect, and it works well.
> [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)