You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "Vinoth Chandar (Jira)" <ji...@apache.org> on 2024/05/03 01:46:00 UTC
[jira] [Commented] (HUDI-7671) Make Hudi timeline backward compatible
[ https://issues.apache.org/jira/browse/HUDI-7671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843109#comment-17843109 ]
Vinoth Chandar commented on HUDI-7671:
--------------------------------------
balaji - this may be a dupe.
> Make Hudi timeline backward compatible
> --------------------------------------
>
> Key: HUDI-7671
> URL: https://issues.apache.org/jira/browse/HUDI-7671
> Project: Apache Hudi
> Issue Type: Improvement
> Components: core
> Reporter: Danny Chen
> Assignee: Balaji Varadarajan
> Priority: Major
> Labels: compatibility
> Fix For: 1.0.0
>
>
> Since release 1.x, the timeline metadata file name is changed to include the completion time, we need to keep compatibility for 0.x branches/releases.
> 0.x meta file name pattern: ${instant_time}.action[.state]
> 1.x meta file name pattern: ${instant_time}_${completion_time}.action[.state].
> In 1.x release, while decipher the Hudi instant from the metadata files, if there is no completion time, uses the file modification time as the completion time instead.
> The modification time follows the OCC concurrency control semantics if the files were not moved around.
> Caution that if the table is a MOR table and the files got moved in history from old folder to the current folder, the reader view may represent wong result set because the completion time are completely the same for all the alive instants.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)