You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Ethan Guo (Jira)" <ji...@apache.org> on 2023/09/06 17:58:00 UTC
[jira] [Closed] (HUDI-6759) Some of the valid instants in MDT are ignored
[ https://issues.apache.org/jira/browse/HUDI-6759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Guo closed HUDI-6759.
---------------------------
Resolution: Fixed
> Some of the valid instants in MDT are ignored
> ---------------------------------------------
>
> Key: HUDI-6759
> URL: https://issues.apache.org/jira/browse/HUDI-6759
> Project: Apache Hudi
> Issue Type: Bug
> Components: metadata
> Reporter: sivabalan narayanan
> Assignee: sivabalan narayanan
> Priority: Major
> Labels: pull-request-available
>
> We do have some special instants times like initialization instant times, compaction, clean etc in MDT timeline.
> During InstantRange check, these should be considered as valid. Especially with MDT partition initialization, the suffix is dynamic, and so we can't really find exact match.So, might have to go with total instant time length and treat all special instant times as valid ones.
> In the LogRecordReader, we will first ignore any uncommitted instants. And then if its completed in MDT timeline, we check w/ the instantRange. and so its should be fine to return true for any special instant times.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)