You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jing Zhang (Jira)" <ji...@apache.org> on 2022/01/10 13:38:00 UTC
[jira] [Updated] (FLINK-25592) Improvement of parser, optimizer and execution for Flink Batch SQL
[ https://issues.apache.org/jira/browse/FLINK-25592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jing Zhang updated FLINK-25592:
-------------------------------
Description:
This is a parent JIRA to track improvements on Flink Batch SQL, including parser, optimizer and execution.
For example,
1. using Hive dialect and default dialect, some sql query would be translated into different plans
2. specify hash/sort aggregate strategy and hash/sortmerge join strategy in sql hint
3. take parquet metadata into consideration in optimization
4. ....
was:
This is a parent JIRA to track all improvements on Flink Batch SQL, including parser, optimizer and execution.
For example,
1. using Hive dialect and default dialect, some sql query would be translated into different plans
2. specify hash/sort aggregate strategy and hash/sortmerge join strategy in sql hint
3. take parquet metadata into consideration in optimization
4. ....
> Improvement of parser, optimizer and execution for Flink Batch SQL
> ------------------------------------------------------------------
>
> Key: FLINK-25592
> URL: https://issues.apache.org/jira/browse/FLINK-25592
> Project: Flink
> Issue Type: Improvement
> Reporter: Jing Zhang
> Priority: Minor
>
> This is a parent JIRA to track improvements on Flink Batch SQL, including parser, optimizer and execution.
> For example,
> 1. using Hive dialect and default dialect, some sql query would be translated into different plans
> 2. specify hash/sort aggregate strategy and hash/sortmerge join strategy in sql hint
> 3. take parquet metadata into consideration in optimization
> 4. ....
--
This message was sent by Atlassian Jira
(v8.20.1#820001)