You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "Sagar Sumit (Jira)" <ji...@apache.org> on 2025/01/09 00:56:00 UTC

[jira] [Closed] (HUDI-8518) Seondary index should work with all merge modes

     [ https://issues.apache.org/jira/browse/HUDI-8518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sagar Sumit closed HUDI-8518.
-----------------------------
    Resolution: Fixed

> Seondary index should work with all merge modes
> -----------------------------------------------
>
>                 Key: HUDI-8518
>                 URL: https://issues.apache.org/jira/browse/HUDI-8518
>             Project: Apache Hudi
>          Issue Type: Sub-task
>            Reporter: Sagar Sumit
>            Assignee: Sagar Sumit
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.0.1
>
>   Original Estimate: 20h
>  Remaining Estimate: 20h
>
> Currently, secondary index just looks at the file slices part of the commit metadata, assuming that the index must be correct for previous versions. This all works good with overwrite with latest payload. But, if someone is using custom payload, then index records should be prepared while looking at all file slices merged for a filegroup according to the custom payload.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)