[
https://issues.apache.org/jira/browse/HIVE-21344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesus Camacho Rodriguez updated HIVE-21344:
-------------------------------------------
Description:
For every query, {{getAllValidMaterializedViews}} still requires a call to
metastore to verify that the materializations exist, whether they are outdated
or not, etc. Since this is only useful for active-active HS2 deployments, we
could take a less aggressive approach and check this information only after
rewriting has been triggered. In addition, we could refresh the information in
the HS2 registry periodically in a background thread.
{code}
// This is not a rebuild, we retrieve all the materializations. In turn, we do
not need
// to force the materialization contents to be up-to-date, as this is not a
rebuild, and
// we apply the user parameters (HIVE_MATERIALIZED_VIEW_REWRITING_TIME_WINDOW)
instead.
materializations = db.getAllValidMaterializedViews(getTablesUsed(basePlan),
false, getTxnMgr());
{code}
!mv-get-from-remote.png!
was:
registry is not used for Calcite planner.
{code}
// This is not a rebuild, we retrieve all the materializations. In turn, we do
not need
// to force the materialization contents to be up-to-date, as this is
not a rebuild, and
// we apply the user parameters
(HIVE_MATERIALIZED_VIEW_REWRITING_TIME_WINDOW) instead.
materializations =
db.getAllValidMaterializedViews(getTablesUsed(basePlan), false, getTxnMgr());
}
{code}
!mv-get-from-remote.png!
> CBO: Reduce compilation time in presence of materialized views
> --------------------------------------------------------------
>
> Key: HIVE-21344
> URL: https://issues.apache.org/jira/browse/HIVE-21344
> Project: Hive
> Issue Type: Bug
> Components: Materialized views
> Affects Versions: 4.0.0
> Reporter: Gopal V
> Assignee: Jesus Camacho Rodriguez
> Priority: Major
> Attachments: calcite-planner-after-fix.svg.zip, mv-get-from-remote.png
>
>
> For every query, {{getAllValidMaterializedViews}} still requires a call to
> metastore to verify that the materializations exist, whether they are
> outdated or not, etc. Since this is only useful for active-active HS2
> deployments, we could take a less aggressive approach and check this
> information only after rewriting has been triggered. In addition, we could
> refresh the information in the HS2 registry periodically in a background
> thread.
> {code}
> // This is not a rebuild, we retrieve all the materializations. In turn, we
> do not need
> // to force the materialization contents to be up-to-date, as this is not a
> rebuild, and
> // we apply the user parameters
> (HIVE_MATERIALIZED_VIEW_REWRITING_TIME_WINDOW) instead.
> materializations = db.getAllValidMaterializedViews(getTablesUsed(basePlan),
> false, getTxnMgr());
> {code}
> !mv-get-from-remote.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
