[
https://issues.apache.org/jira/browse/HIVE-20006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16544043#comment-16544043
]
Hive QA commented on HIVE-20006:
--------------------------------
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12931576/HIVE-20006.07.patch
{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.
{color:green}SUCCESS:{color} +1 due to 14648 tests passed
Test results:
https://builds.apache.org/job/PreCommit-HIVE-Build/12600/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/12600/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-12600/
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}
This message is automatically generated.
ATTACHMENT ID: 12931576 - PreCommit-HIVE-Build
> Make materializations invalidation cache work with multiple active remote
> metastores
> ------------------------------------------------------------------------------------
>
> Key: HIVE-20006
> URL: https://issues.apache.org/jira/browse/HIVE-20006
> Project: Hive
> Issue Type: Improvement
> Components: Materialized views
> Affects Versions: 3.0.0
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Priority: Critical
> Attachments: HIVE-19027.01.patch, HIVE-19027.02.patch,
> HIVE-19027.03.patch, HIVE-19027.04.patch, HIVE-20006.01.patch,
> HIVE-20006.02.patch, HIVE-20006.03.patch, HIVE-20006.04.patch,
> HIVE-20006.05.patch, HIVE-20006.06.patch, HIVE-20006.07.patch,
> HIVE-20006.patch
>
>
> The main points:
> - Only MVs that use transactional tables and are stored in transactional
> tables can have a time window value of 0. Those are the only MVs that can be
> guaranteed to not be outdated when a query is executed.
> - For MVs that +cannot be outdated+, comparison is based on valid write id
> lists.
> - For MVs that +can be outdated+:
> ** The window for valid outdated MVs can be specified in intervals of 1
> minute.
> ** A materialized view is outdated if it was built before that time window
> and any source table has been modified since.
> A time window of -1 means to always use the materialized view for rewriting
> without any checks concerning its validity. If a materialized view uses an
> external table, the only way to trigger the rewriting would be to set the
> property to -1, since currently we do not capture for validation purposes
> whether the external source tables have been modified since the MV was
> created or not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
