[
https://issues.apache.org/jira/browse/HIVE-22111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16956488#comment-16956488
]
Jesus Camacho Rodriguez commented on HIVE-22111:
------------------------------------------------
I have just seen this issue again. If we are replicating the creation metadata
for the materialized views, then we cannot just set the flag to 'N'; indeed as
a workaround, we could set it to 'Y' even if we fallback to full rebuild first
time we rebuild the materialized view in the cluster with the replica.
AFAIK, materialized views replication has other problems right now wrt
replication, see HIVE-18621 and HIVE-20543.
> Materialized view based on replicated table might not get refreshed
> -------------------------------------------------------------------
>
> Key: HIVE-22111
> URL: https://issues.apache.org/jira/browse/HIVE-22111
> Project: Hive
> Issue Type: Bug
> Components: Materialized views, repl
> Reporter: Peter Vary
> Assignee: Peter Vary
> Priority: Minor
>
> Consider the following scenario:
> * create a base table which we replicate
> * create a materialized view in the target hive based on the base table
> * modify (delete/update) the base table in the source hive
> * replicate the changes (delete/update) to the target hive
> * query the materialized view in the target hive
>
> We do not refresh the data, since when the transaction is created by
> replication we set ctc_update_delete to 'N'.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
