[CALCITE-3448] AggregateOnCalcToAggregateUnifyRule ignores Project incorrectly when there's missing grouping or mapping breaks ordering

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.22.0
• Component/s: core
• Labels: pull-request-available
• Assignee: Jin Xing
• Reporter: Jin Xing
• Created: 25/Oct/19 13:08
• Updated: 06/Mar/20 04:35
• Resolved: 12/Nov/19 18:45

Description

CALCITE-3087 fixed AggregateOnProjectToAggregateUnifyRule when mapping under Aggregate breaks ordering. But it fails when there's missing grouping in query compared with target.
Below matching fails:

MV:
 select empid, deptno, name, count(*) from emps
 group by empid, deptno, name
Query:
 select name, empid, count(*) from emps group by name, empid

Note that – comparing groupings in MV (empid, deptno, name) and groupings in query (name, empid), deptno is missed and ordering is broken

Issue Links

• relates to: CALCITE-3087 AggregateOnProjectToAggregateUnifyRule ignores Project incorrectly when its Mapping breaks ordering
• links to: GitHub Pull Request #1532