Concurrency control for LSM timeline management and writing.(phase-2)
Open
from-jira
priority:critical
type:improvement
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-7545
- Type: Improvement
- Epic: https://issues.apache.org/jira/browse/HUDI-6698
- Fix version(s):
- 1.1.0
---
## Comments
21/Sep/24 01:06;danny0405;Currently, we always add a lock for archiving(again table service and multi-writer scenarios), maybe we can re-consider this when all the archiving logic is moved to the LSM timeline itself, before that we need to ensure the commits to archive do not have overlap, so there is no need to have specific concurrency control IMO, we can introduce async compaction if that could be a overhead in the near feature.;;;
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.