You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Krisztian Kasa (Jira)" <ji...@apache.org> on 2021/11/29 10:44:00 UTC
[jira] [Updated] (HIVE-25656) Get materialized view state based on number of affected rows of transactions
[ https://issues.apache.org/jira/browse/HIVE-25656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Krisztian Kasa updated HIVE-25656:
----------------------------------
Component/s: Thrift API
> Get materialized view state based on number of affected rows of transactions
> ----------------------------------------------------------------------------
>
> Key: HIVE-25656
> URL: https://issues.apache.org/jira/browse/HIVE-25656
> Project: Hive
> Issue Type: Improvement
> Components: Materialized views, Thrift API, Transactions
> Reporter: Krisztian Kasa
> Assignee: Krisztian Kasa
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> To enable the faster incremental rebuild of materialized views presence of update/delete operations on the source tables of the view since the last rebuild must be checked. Based on the outcome different plan is generated for scenarios in presence of update/delete and insert only operations.
> Currently this is done by querying the COMPLETED_TXN_COMPONENTS table however the records from this table is cleaned when MV source tables are compacted. This reduces the chances of incremental MV rebuild.
> The goal of this patch is to find an alternative way to store and retrieve this information.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)