[jira] [Commented] (HIVE-20006) Make materializations invalidation cache work with multiple active remote metastores

["Hive QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-20006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526200#comment-16526200 ] 

Hive QA commented on HIVE-20006:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12929351/HIVE-20006.patch

{color:green}SUCCESS:{color} +1 due to 2 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 3 failed/errored test(s), 14587 tests executed
*Failed tests:*
{noformat}
TestReplicationScenariosAcrossInstances - did not produce a TEST-*.xml file (likely timed out) (batchId=238)
org.apache.hadoop.hive.cli.TestMiniDruidCliDriver.testCliDriver[druid_timestamptz] (batchId=191)
org.apache.hadoop.hive.cli.TestMiniDruidCliDriver.testCliDriver[druidmini_joins] (batchId=191)
{noformat}

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/12208/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/12208/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-12208/

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
Tests exited with: TestsFailedException: 3 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12929351 - 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.patch
>
>
> The main points:
>  - Only MVs 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, if we use custom storage handlers to store the materialized view, we cannot make any promises.
>  - For MVs that +cannot be outdated+, we do not check the metastore. Instead, comparison is based on valid write id lists.
>  - For MVs that +can be outdated+, we still rely on the invalidation cache.
>  ** The window for valid outdated MVs can be specified in intervals of 1 minute (less than that, it is difficult to have any guarantees about whether the MV is actually outdated by less than a minute or not).
>  ** The async loading is done every interval / 2 (or probably better, we can make it configurable).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)