[
https://issues.apache.org/jira/browse/BEAM-8794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Kozlov updated BEAM-8794:
--------------------------------
Status: Open (was: Triage Needed)
> Projects should be handled by an IOPushDownRule before applying
> AggregateProjectMergeRule
> -----------------------------------------------------------------------------------------
>
> Key: BEAM-8794
> URL: https://issues.apache.org/jira/browse/BEAM-8794
> Project: Beam
> Issue Type: Improvement
> Components: dsl-sql
> Reporter: Kirill Kozlov
> Assignee: Kirill Kozlov
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It is more efficient to push-down projected fields at an IO level (vs merging
> with an Aggregate), when supported.
> When running queries like:
> {code:java}
> select SUM(score) as total_score from <TABLE> group by name{code}
> Projects get merged with an aggregate, as a result Calc (after an
> IOSourceRel) projects all fields and BeamIOPushDown rule does know what
> fields can be dropped, thus not dropping any.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
