You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Krisztian Kasa (Jira)" <ji...@apache.org> on 2020/10/14 14:35:00 UTC

[jira] [Assigned] (HIVE-24274) Implement Query Text based MaterializedView rewrite

     [ https://issues.apache.org/jira/browse/HIVE-24274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krisztian Kasa reassigned HIVE-24274:
-------------------------------------


> Implement Query Text based MaterializedView rewrite
> ---------------------------------------------------
>
>                 Key: HIVE-24274
>                 URL: https://issues.apache.org/jira/browse/HIVE-24274
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Krisztian Kasa
>            Assignee: Krisztian Kasa
>            Priority: Major
>
> Besides the way queries are currently rewritten to use materialized views in Hive this project provides an alternative:
> Compare the query text with the materialized views query text stored. If we found a match the original query's logical plan can be replaced by a scan on the materialized view.
> - Only materialized views which are enabled to rewrite can participate
> - Use existing *HiveMaterializedViewsRegistry* through *Hive* object by adding a lookup method by query text.
> - There might be more than one materialized views which have the same query text. In this case chose the first valid one.
> - Validation can be done by calling *Hive.validateMaterializedViewsFromRegistry()*
> - The scope of this first patch is rewriting queries which entire text can be matched only.
> - Use the expanded query text (fully qualified column and table names) for comparing



--
This message was sent by Atlassian Jira
(v8.3.4#803005)