[
https://issues.apache.org/jira/browse/FLINK-30242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-30242:
-----------------------------------
Labels: pull-request-available stale-major (was: 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
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 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.
> Push localHashAggregate pass the union node
> -------------------------------------------
>
> Key: FLINK-30242
> URL: https://issues.apache.org/jira/browse/FLINK-30242
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Reporter: Aitozi
> Priority: Major
> Labels: pull-request-available, stale-major
> Attachments: screenshot-1.png, screenshot-2.png
>
>
> The local hash aggregate after union will have an extra shuffle stage. We can
> swap it with the union node so the local hash aggregate can chain with the
> mapper stage saving the unnecessary shuffle, especially in the batch job.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
