[
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-deprioritized-major auto-deprioritized-minor auto-unassigned
(was: auto-deprioritized-major auto-unassigned stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned
>
> 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.20.10#820010)
