You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "sivabalan narayanan (Jira)" <ji...@apache.org> on 2025/04/09 20:14:00 UTC
[jira] [Updated] (HUDI-9171) Revisit all indexes to account for DELETE_PARTITION
[ https://issues.apache.org/jira/browse/HUDI-9171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
sivabalan narayanan updated HUDI-9171:
--------------------------------------
Remaining Estimate: 8h
Original Estimate: 8h
> Revisit all indexes to account for DELETE_PARTITION
> ---------------------------------------------------
>
> Key: HUDI-9171
> URL: https://issues.apache.org/jira/browse/HUDI-9171
> Project: Apache Hudi
> Issue Type: Sub-task
> Reporter: Sagar Sumit
> Priority: Major
> Fix For: 1.1.0
>
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> Not all indexes are strictly consistent after DELETE_PARTITION. Files is consistent and we made partition stats consistent in HUDI-8345. However, column_stats is only eventually consistent. Basically, the stats for replaced filegroups get deleted when those file groups are cleaned. This is ok because we don't use column_stats in partition pruning. But, we should consider making this check general and make other index types also consider the {{DELETE_PARTITION}} write operation in a distinct way?
> https://github.com/apache/hudi/pull/12953#discussion_r1990324655
--
This message was sent by Atlassian Jira
(v8.20.10#820010)