[HIVE-22253] General task tracking improvements for materialized views

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Materialized views
• Assignee: Unassigned
• Reporter: Steve Carlin
• Created: 27/Sep/19 20:34
• Updated: 20/Jul/20 13:30

Description

We have a whole lot of tests from a different system that created and tested materialized views.

This Jira serves as the parent task for all the shortcomings that were found when running these tests on Hive

Issue Links

• is related to: HIVE-23884 SemanticAnalyzer exception when addressing field with table name in group by

Sub-Tasks

• Support for materialized view rewriting with window functions: Closed
• MV rewriting for distinct and count(distinct) not being triggered: Closed
• Rewriting fails when `IN` clause has items in different order in MV and query: Closed
• Rewriting fails for `IN` clauses in MV and query when we use equals or subset in the query: Closed
• Rewriting fails for `BETWEEN` clauses with different ranges in MV and query: Closed
• Aggregate pushdown through join may generate additional rewriting opportunities: Open
• Ordinals in view are not being picked up in materialized view: Open
• Mappings.NoElementException: no target in mapping, in `MaterializedViewAggregateRule: Closed
• Commutativity of operations is not taken into account, e.g., '+': Closed
• Materialized view rewriting does not support `UNION` operator, exact match can work under view: Open
• Degenerate case where mv not being used: computing aggregate on group by field: Open
• Aggregate after join throws off MV rewrite: Closed
• Support for rewriting with materialized views containing grouping sets: Closed
• Add support for `intersect` keyword in MV: Closed
• MV query fails with CalciteViewSemanticException: Resolved
• MV fails for queries with subqueries: Resolved
• Optimize MV: Materialized views should not rebuild when tables are not modified: Resolved
• Allow triggering materialized view rewriting for external tables: Resolved