[
https://issues.apache.org/jira/browse/HIVE-18387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352030#comment-16352030
]
Jesus Camacho Rodriguez edited comment on HIVE-18387 at 2/5/18 4:57 AM:
------------------------------------------------------------------------
[~ashutoshc], I have rebased this patch after HIVE-18546 went in, this might go
in before HIVE-18259. Could you take a look?
https://reviews.apache.org/r/65250/
I created HIVE-18621 as a follow-up to this issue. Replication does not work
properly for views and materialized views yet, hence I think it can be tackled
there.
was (Author: jcamachorodriguez):
[~ashutoshc], I have rebased this patch after HIVE-18546 went in, this might go
in before HIVE-18387. Could you take a look?
https://reviews.apache.org/r/65250/
I created HIVE-18621 as a follow-up to this issue. Replication does not work
properly for views and materialized views yet, hence I think it can be tackled
there.
> Minimize time that REBUILD locks the materialized view
> ------------------------------------------------------
>
> Key: HIVE-18387
> URL: https://issues.apache.org/jira/browse/HIVE-18387
> Project: Hive
> Issue Type: Improvement
> Components: Materialized views
> Affects Versions: 3.0.0
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Priority: Major
> Attachments: HIVE-18387.01.patch, HIVE-18387.02.patch,
> HIVE-18387.03.patch, HIVE-18387.patch
>
>
> Currently, REBUILD will block the materialized view while the final move task
> is being executed. The idea for this improvement is to create the new
> materialization in a new folder (new version) and then just flip the pointer
> to the folder in the MV definition in the metastore. REBUILD operations for a
> given MV should get an exclusive lock though, i.e., they cannot be executed
> concurrently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
