You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Alan Gates (JIRA)" <ji...@apache.org> on 2015/04/23 06:20:38 UTC

[jira] [Updated] (HIVE-10459) Add materialized views to Hive

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

Alan Gates updated HIVE-10459:
------------------------------
    Attachment: HIVE-10459.patch

This patch is a start at implementing simple views.  It doesn't have enough testing yet (e.g. there's no negative testing).  And I know it fails in the partitioned case.  I suspect things like security and locking don't work properly yet either.  But I'm posting it as a starting point.

In this initial patch I'm just handling simple materialized views with manual rebuilds.  In later JIRAs we can add features such as allowing the optimizer to rewrite queries to use materialized views rather than tables named in the queries, giving the optimizer the ability to determine when a materialized view is stale, etc.

Also, I didn't rebase this patch against trunk after the migration from svn->git so it may not apply cleanly.

> Add materialized views to Hive
> ------------------------------
>
>                 Key: HIVE-10459
>                 URL: https://issues.apache.org/jira/browse/HIVE-10459
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>         Attachments: HIVE-10459.patch
>
>
> Materialized views are useful as ways to store either alternate versions of data (e.g. same data, different sort order) or derivatives of data sets (e.g. commonly used aggregates).  It is useful to store these as materialized views rather than as tables because it can give the optimizer the ability to understand how data sets are related.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)