[
https://issues.apache.org/jira/browse/HUDI-3798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sivabalan narayanan updated HUDI-3798:
--------------------------------------
Description:
As of now, transaction manager is designed in such a way that no two writers
can access it concurrently. Some state is being shared among all callers like
currentTxnOwnerInstant, lastCompletedTxnOwner. Lets revisit this and ensure
lock manager is the one which manages the concurrency, but txn manager is just
a proxy for it.
Also fix the usages of different beginTransaction methods.
Ref: [https://github.com/apache/hudi/pull/4363#pullrequestreview-915499359]
was:
As of now, transaction manager is designed in such a way that no two writers
can access it concurrently. Some state is being shared among all callers like
currentTxnOwnerInstant, lastCompletedTxnOwner. Lets revisit this and ensure
lock manager is the one which manages the concurrency, but txn manager is just
a proxy for it.
> Allow TransactionManager to work w/ multiple txn owners
> -------------------------------------------------------
>
> Key: HUDI-3798
> URL: https://issues.apache.org/jira/browse/HUDI-3798
> Project: Apache Hudi
> Issue Type: Task
> Reporter: sivabalan narayanan
> Assignee: sivabalan narayanan
> Priority: Blocker
> Fix For: 0.11.0
>
>
> As of now, transaction manager is designed in such a way that no two writers
> can access it concurrently. Some state is being shared among all callers like
> currentTxnOwnerInstant, lastCompletedTxnOwner. Lets revisit this and ensure
> lock manager is the one which manages the concurrency, but txn manager is
> just a proxy for it.
>
> Also fix the usages of different beginTransaction methods.
>
> Ref: [https://github.com/apache/hudi/pull/4363#pullrequestreview-915499359]
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
