You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/06/03 23:34:01 UTC

[jira] [Updated] (FLINK-15734) Support spill in batch hash window aggregation

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

Flink Jira Bot updated FLINK-15734:
-----------------------------------
    Labels: stale-major  (was: )

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 Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Support spill in batch hash window aggregation
> ----------------------------------------------
>
>                 Key: FLINK-15734
>                 URL: https://issues.apache.org/jira/browse/FLINK-15734
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Runtime
>            Reporter: Jingsong Lee
>            Priority: Major
>              Labels: stale-major
>
> We can fallback to sort aggregation like regular aggregate instead of bothering user to change to sort agg or increase memory.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)