[
https://issues.apache.org/jira/browse/FLINK-20791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20791:
-----------------------------------
Labels: auto-unassigned stale-major (was: auto-unassigned)
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.
> Support local aggregate push down for Blink batch planner
> ---------------------------------------------------------
>
> Key: FLINK-20791
> URL: https://issues.apache.org/jira/browse/FLINK-20791
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API, Table SQL / Planner
> Reporter: Sebastian Liu
> Priority: Major
> Labels: auto-unassigned, stale-major
>
> Aggregate operator of Flink SQL is currently fully done at Flink layer. With
> the developing of storage, many downstream storage of Flink SQL has the
> ability to deal with Aggregation operator.
> Pushing down Aggregate to data source layer will improve performance from the
> perspective of the network IO and computation overhead.
>
> I have drafted a design doc for this new feature.
> [https://docs.google.com/document/d/1kGwC_h4qBNxF2eMEz6T6arByOB8yilrPLqDN0QBQXW4/edit?usp=sharing]
>
> Any comment or discussion is welcome.
> Discuss thread:
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Support-local-aggregate-push-down-for-Blink-batch-planner-td47439.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
