hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-14249) Add simple materialized views with manual rebuilds
Date Thu, 25 Aug 2016 20:11:21 GMT


Hive QA commented on HIVE-14249:

Here are the results of testing the latest attachment:

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

{color:red}ERROR:{color} -1 due to 10 failed/errored test(s), 10482 tests executed
*Failed tests:*

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 10 tests failed

This message is automatically generated.

ATTACHMENT ID: 12825412 - PreCommit-HIVE-MASTER-Build

> Add simple materialized views with manual rebuilds
> --------------------------------------------------
>                 Key: HIVE-14249
>                 URL:
>             Project: Hive
>          Issue Type: New Feature
>          Components: Materialized views, Parser
>            Reporter: Alan Gates
>            Assignee: Jesus Camacho Rodriguez
>         Attachments: HIVE-10459.2.patch, HIVE-14249.05.patch
> This patch is a start at implementing simple views. It doesn't have enough testing yet
(e.g. there's no negative testing). And I know it fails in the partitioned case. I suspect
things like security and locking don't work properly yet either. But I'm posting it as a starting
> In this initial patch I'm just handling simple materialized views with manual rebuilds.
In later JIRAs we can add features such as allowing the optimizer to rewrite queries to use
materialized views rather than tables named in the queries, giving the optimizer the ability
to determine when a materialized view is stale, etc.
> Also, I didn't rebase this patch against trunk after the migration from svn->git so
it may not apply cleanly.

This message was sent by Atlassian JIRA

View raw message