[
https://issues.apache.org/jira/browse/HIVE-28050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815170#comment-17815170
]
Stamatis Zampetakis commented on HIVE-28050:
--------------------------------------------
Hey [~kkasa], I see that the PR removes code so I assume we are removing the
feature introduced by HIVE-24854 is that correct? Is there a plan to restore
the functionality in the future?
Can you briefly outline here why it is impossible to fix the existing code and
instead you opted for removal?
> Disable Incremental non aggregated materialized view rebuild in presence of
> delete operations
> ---------------------------------------------------------------------------------------------
>
> Key: HIVE-28050
> URL: https://issues.apache.org/jira/browse/HIVE-28050
> Project: Hive
> Issue Type: Bug
> Components: Materialized views
> Reporter: Krisztian Kasa
> Assignee: Krisztian Kasa
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> To support incremental rebuild of materialized views which definition does
> not have aggregate in presence of delete operations in any of its source
> tables the records of the source tables need to be uniquely identified and
> joined with the records present in the view.
> One possibility is to project ROW_IDs of each source table in the view
> definition but the writeId component is changing at delete.
> Another way is to project columns of primary keys or unique keys but these
> constraints are not enforced in Hive.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
