[
https://issues.apache.org/jira/browse/HUDI-6356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagar Sumit closed HUDI-6356.
-----------------------------
Fix Version/s: 0.14.0
Assignee: Surya Prasanna Yalla
Resolution: Fixed
> Fix rollback logic on AbstractHoodieLogRecordReader when replacecommits in
> main table are retried and created log blocks in metadata table.
> -------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HUDI-6356
> URL: https://issues.apache.org/jira/browse/HUDI-6356
> Project: Apache Hudi
> Issue Type: Bug
> Reporter: Surya Prasanna Yalla
> Assignee: Surya Prasanna Yalla
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.14.0
>
>
> On metadata table deltacommmit timestamp is equivalent to main table commit's
> timestamp. So, if metadata sync fails it reuses the same timestamp. This
> change fixes the case where the log blocks are treated as valid if their
> corresponding rollback is already visited.
> So, rollback block follow the ordering and do not effect the blocks that
> arrive later.
> Ex:
> LogBlock1 (Data log block with instant1)
> LogBlock2 (Data log block with instant2)
> LogBlock3 (Rollback block with instant3 and rolling back instant2)
> LogBlock4 (Data log block with instant2)
> After processing this change returns LogBlock1 and LogBlock4 as valid blocks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
