[
https://issues.apache.org/jira/browse/HUDI-7030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Danny Chen closed HUDI-7030.
----------------------------
Resolution: Fixed
Fixed via master branch: e731755b99057dc916378f1f7e95c73642ff96e8
> Log reader data lost as that not consistent behavior in timeline's
> containsInstant
> -----------------------------------------------------------------------------------
>
> Key: HUDI-7030
> URL: https://issues.apache.org/jira/browse/HUDI-7030
> Project: Apache Hudi
> Issue Type: Bug
> Affects Versions: 0.14.0
> Reporter: ann
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0, 0.14.1
>
> Attachments: image-2023-11-03-19-48-29-441.png,
> image-2023-11-03-19-49-22-894.png, image-2023-11-03-19-50-11-849.png,
> image-2023-11-03-19-58-39-495.png, image-2023-11-03-20-06-00-579.png,
> image-2023-11-03-20-06-13-905.png, image-2023-11-03-20-07-30-201.png
>
>
> Log reader filtered all log data blocks which come from inflight instant.
> !image-2023-11-03-19-49-22-894.png!
> *containsInstant* return false when input instant's timestamp is not equal as
> anyone instant timestamp in inflight timeline.
> !image-2023-11-03-20-07-30-201.png!
> But now, in timeline's *containsInstant* that input is instant's timestamp,
> it would return true.
>
> When input is the instant with default_millis_ext, instant's timestamp is
> less than someone instant timestamp in timeline.
> !image-2023-11-03-19-50-11-849.png!
> In finally, log reader skipped the completed delta commit instant and caused
> data lost.
> !image-2023-11-03-19-58-39-495.png!
> I think timeline's containsInstant should have consistent behavior and update
> containsOrBeforeTimelineStarts to containsInstant
> !image-2023-11-03-19-48-29-441.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
