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

ASF GitHub Bot updated HUDI-6152:
---------------------------------
    Labels: pull-request-available  (was: )

> Check for valid commit during tagLocation does not handle mixed timestamps in 
> the dataset
> -----------------------------------------------------------------------------------------
>
>                 Key: HUDI-6152
>                 URL: https://issues.apache.org/jira/browse/HUDI-6152
>             Project: Apache Hudi
>          Issue Type: Bug
>            Reporter: Prashant Wason
>            Assignee: Prashant Wason
>            Priority: Major
>              Labels: pull-request-available
>
> If both pre-0.10 sec level timestamp and 0.10+ msec level timestamps exist in 
> the timeline then checkIfValidCommit does not correctly perform the check. 
> This is because the new msec timestamp format adds a 999 suffix to older 
> timestamps.



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

Reply via email to