[jira] [Updated] (FLINK-15004) Choose two-phase Aggregate if the statistics is unknown

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-15004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-15004:
-----------------------------------
    Labels: auto-deprioritized-major auto-unassigned pull-request-available stale-minor  (was: auto-deprioritized-major auto-unassigned pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Choose two-phase Aggregate if the statistics is unknown
> -------------------------------------------------------
>
>                 Key: FLINK-15004
>                 URL: https://issues.apache.org/jira/browse/FLINK-15004
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Planner
>    Affects Versions: 1.9.1, 1.10.0
>            Reporter: godfrey he
>            Priority: Minor
>              Labels: auto-deprioritized-major, auto-unassigned, pull-request-available, stale-minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, blink planner will use default rowCount value (defined in {{FlinkPreparingTableBase#DEFAULT_ROWCOUNT}} ) when the statistics is unknown, and maybe choose one-phase Aggregate. The job will hang if the data is skewed. So It's better to use two-phase Aggregate for execution stability if the statistics is unknown.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)