[
https://issues.apache.org/jira/browse/HUDI-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17900180#comment-17900180
]
Y Ethan Guo edited comment on HUDI-8464 at 11/21/24 9:08 PM:
-------------------------------------------------------------
Makes sense. When we support NBCC for concurrent updates and clustering
(HUDI-1045), we also need to keep this in mind for clustering since there is a
time gap between clustering request time generation and adding clustering
requested file on timeline after the clustering planning, i.e., clustering
planning need to consider the requested time of the clustering too.
was (Author: JIRAUSER280684):
Makes sense. When we support NBCC for concurrent updates and clustering
(HUDI-1045), we also need to keep this in mind for clustering since there is a
time gap between clustering request time generation and adding clustering
requested file on timeline after the clustering planning.
> Strengthen TrueTime API and locking
> -----------------------------------
>
> Key: HUDI-8464
> URL: https://issues.apache.org/jira/browse/HUDI-8464
> Project: Apache Hudi
> Issue Type: Improvement
> Reporter: Y Ethan Guo
> Assignee: Vinoth Chandar
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.0.0
>
> Attachments: image-2024-11-21-06-05-26-888.png,
> image-2024-11-21-07-00-33-053.png
>
> Original Estimate: 6h
> Remaining Estimate: 6h
>
> For serializability and strict time ordering, we should provide Spanner's
> TrueTime guarantee, i.e., lock and wait for a time period considering the
> practical largest clock skew (e.g., 500ms) before generating a new time, so
> that the time generated is always monotonically increasing for both instant
> time and completion time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
