hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-19027) Make materializations invalidation cache work with multiple active remote metastores
Date Mon, 25 Jun 2018 08:42:00 GMT

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

Hive QA commented on HIVE-19027:
--------------------------------



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

{color:red}ERROR:{color} -1 due to build exiting with an error

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

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Tests exited with: Exception: Patch URL https://issues.apache.org/jira/secure/attachment/12928934/HIVE-19027.02.patch
was found in seen patch url's cache and a test was probably run already on it. Aborting...
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12928934 - PreCommit-HIVE-Build

> Make materializations invalidation cache work with multiple active remote metastores
> ------------------------------------------------------------------------------------
>
>                 Key: HIVE-19027
>                 URL: https://issues.apache.org/jira/browse/HIVE-19027
>             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
>
>
> 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)

Mime
View raw message