You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Martijn Visser (Jira)" <ji...@apache.org> on 2022/07/05 09:08: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 ]

Martijn Visser updated FLINK-25592:
-----------------------------------
    Fix Version/s: 1.16.0

> 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
>          Components: Table SQL / API, Table SQL / Planner, Table SQL / Runtime
>            Reporter: Jing Zhang
>            Priority: Major
>             Fix For: 1.16.0
>
>
> 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/sort merge join strategy in sql hint
> 3. take parquet metadata into consideration in optimization
> 4. and so on
> Please note, some improvements are not limited to batch sql. Maybe streaming sql job could also benefits from some improvements in this JIRA.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)