[ 
https://issues.apache.org/jira/browse/HIVE-26375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Krisztian Kasa resolved HIVE-26375.
-----------------------------------
    Resolution: Fixed

Pushed to master. Thanks [~lpinter] and [~amansinha100] for review.

> Invalid materialized view after rebuild if source table was compacted
> ---------------------------------------------------------------------
>
>                 Key: HIVE-26375
>                 URL: https://issues.apache.org/jira/browse/HIVE-26375
>             Project: Hive
>          Issue Type: Bug
>          Components: Materialized views, Transactions
>            Reporter: Krisztian Kasa
>            Assignee: Krisztian Kasa
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> After HIVE-25656 MV state depends on the number of rows deleted/updated in 
> the source tables of the view. However if one of the source tables are major 
> compacted the delete delta files are no longer available and reproducing the 
> rows should be deleted from the MV is no longer possible.
> {code}
> create table t1(a int, b varchar(128), c float) stored as orc TBLPROPERTIES 
> ('transactional'='true');
> insert into t1(a,b, c) values (1, 'one', 1.1), (2, 'two', 2.2), (NULL, NULL, 
> NULL);
> create materialized view mv1 stored as orc TBLPROPERTIES 
> ('transactional'='true') as select a,b,c from t1 where a > 0 or a is null;
> update t1 set b = 'Changed' where a = 1;
> alter table t1 compact 'major';
> alter materialized view t1 rebuild;
> select * from mv1;
> {code}
> Select should result 
> {code}
>       "1\tChanged\t1.1",
>       "2\ttwo\t2.2",
>       "NULL\tNULL\tNULL"
> {code}
> but was
> {code}
>       "1\tone\t1.1",      
>       "2\ttwo\t2.2",
>       "NULL\tNULL\tNULL",
>       "1\tChanged\t1.1"
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to