[
https://issues.apache.org/jira/browse/HUDI-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinoth Chandar closed HUDI-3187.
--------------------------------
Resolution: Duplicate
> Initiate RFC Lock free concurrency control
> -------------------------------------------
>
> Key: HUDI-3187
> URL: https://issues.apache.org/jira/browse/HUDI-3187
> Project: Apache Hudi
> Issue Type: Improvement
> Components: writer-core
> Reporter: Vinoth Chandar
> Assignee: Vinoth Chandar
> Priority: Blocker
> Fix For: 1.0.0
>
>
> Basic idea here builds on principles laid out here.
> [https://cwiki.apache.org/confluence/display/HUDI/RFC+-+22+%3A+Snapshot+Isolation+using+Optimistic+Concurrency+Control+for+multi-writers#RFC22:SnapshotIsolationusingOptimisticConcurrencyControlformultiwriters-FutureWork(LockFree-ishConcurrencyControl)]
>
>
> At a high level, we want to introduce tracking of "transition_time" to the
> Hudi timeline, where we track the following for each action.
> * start_time (current instant time)
> * action type
> * state (requested, inflight, completed)
> * transition_time (when the action reached that given state)
> Then, we could use this to resolve conflicts during read/query planning time.
> Goal of this task, to write up a detailed design doc around this and
> kickstart this.
> We already have a WIP PR that establishes some feasibility and lays some
> ground work
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
