Jesus Camacho Rodriguez created HIVE-14497:
----------------------------------------------
Summary: Fine control for using materialized views in rewriting
Key: HIVE-14497
URL: https://issues.apache.org/jira/browse/HIVE-14497
Project: Hive
Issue Type: Sub-task
Components: Materialized views
Affects Versions: 2.2.0
Reporter: Jesus Camacho Rodriguez
Follow-up of HIVE-14495. Since the number of materialized views in the system
might grow very large, and query rewriting using materialized views might be
very expensive, we need to include a mechanism to enable/disable materialized
views for query rewriting.
Thus, we should extend the CREATE MATERIALIZED VIEW statement as follows:
{code:sql}
CREATE MATERIALIZED VIEW [IF NOT EXISTS] [db_name.]materialized_view_name
[BUILD DEFERRED]
[ENABLE REWRITE] -- NEW!
[COMMENT materialized_view_comment]
[
[ROW FORMAT row_format]
[STORED AS file_format]
| STORED BY 'storage.handler.class.name' [WITH SERDEPROPERTIES (...)]
]
[LOCATION hdfs_path]
[TBLPROPERTIES (property_name=property_value, ...)]
AS select_statement;
{code}
Further, we should extend the ALTER statement in case we want to change the
behavior of the materialized view after we have created it.
{code:sql}
ALTER MATERIALIZED VIEW [db_name.]materialized_view_name DISABLE REWRITE;
{code}
{code:sql}
ALTER MATERIALIZED VIEW [db_name.]materialized_view_name ENABLE REWRITE;
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)