[jira] [Updated] (FLINK-31767) Improve the implementation for "analyze table" execution on partitioned table
[ https://issues.apache.org/jira/browse/FLINK-31767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-31767: --- Labels: pull-request-available (was: ) > Improve the implementation for "analyze table" execution on partitioned table > - > > Key: FLINK-31767 > URL: https://issues.apache.org/jira/browse/FLINK-31767 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Reporter: Godfrey He >Assignee: Godfrey He >Priority: Major > Labels: pull-request-available > > Currently, for partitioned table, the "analyze table" command will generate a > separate SQL statement for each partition. When there are too many > partitions, the compilation/submission/execution time will be very long. This > issue aims to improve it: we can combine the sql statements for each > partition into one with "union all", and just need to execution one sql. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31767) Improve the implementation for "analyze table" execution on partitioned table
[ https://issues.apache.org/jira/browse/FLINK-31767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Godfrey He updated FLINK-31767: --- Description: Currently, for partitioned table, the "analyze table" command will generate a separate SQL statement for each partition. When there are too many partitions, the compilation/submission/execution time will be very long. This issue aims to improve it: we can combine the sql statements for each partition into one with "union all", and just need to execution one sql. (was: Currently, for partitioned table, ) > Improve the implementation for "analyze table" execution on partitioned table > - > > Key: FLINK-31767 > URL: https://issues.apache.org/jira/browse/FLINK-31767 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Reporter: Godfrey He >Assignee: Godfrey He >Priority: Major > > Currently, for partitioned table, the "analyze table" command will generate a > separate SQL statement for each partition. When there are too many > partitions, the compilation/submission/execution time will be very long. This > issue aims to improve it: we can combine the sql statements for each > partition into one with "union all", and just need to execution one sql. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31767) Improve the implementation for "analyze table" execution on partitioned table
[ https://issues.apache.org/jira/browse/FLINK-31767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Godfrey He updated FLINK-31767: --- Description: Currently, for partitioned table, (was: Currently, ) > Improve the implementation for "analyze table" execution on partitioned table > - > > Key: FLINK-31767 > URL: https://issues.apache.org/jira/browse/FLINK-31767 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Reporter: Godfrey He >Assignee: Godfrey He >Priority: Major > > Currently, for partitioned table, -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-31767) Improve the implementation for "analyze table" execution on partitioned table
[ https://issues.apache.org/jira/browse/FLINK-31767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Godfrey He updated FLINK-31767: --- Summary: Improve the implementation for "analyze table" execution on partitioned table (was: Improve the implementation for "analyze table" execution) > Improve the implementation for "analyze table" execution on partitioned table > - > > Key: FLINK-31767 > URL: https://issues.apache.org/jira/browse/FLINK-31767 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Planner >Reporter: Godfrey He >Assignee: Godfrey He >Priority: Major > > Currently, -- This message was sent by Atlassian Jira (v8.20.10#820010)
