You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kirill Kozlov (Jira)" <ji...@apache.org> on 2020/01/07 22:06:00 UTC
[jira] [Resolved] (BEAM-8794) Projects should be handled by an
IOPushDownRule before applying AggregateProjectMergeRule
[ https://issues.apache.org/jira/browse/BEAM-8794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirill Kozlov resolved BEAM-8794.
---------------------------------
Fix Version/s: 2.18.0
Resolution: Fixed
> 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
> Fix For: 2.18.0
>
> Time Spent: 3h 20m
> 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)