Detect concurrent writes during compaction and clustering if they shouldn't happen
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
During async compaction and clustering jobs, we should ensure that a lock provider is set and concurrent writes are enabled
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-5305
- Type: Improvement
---
## Comments
09/Dec/22 16:54;jonvex;I think this issue is getting moved to someone else because it might be too complex for me;;;
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names async compaction and clustering jobs, a lock provider, and concurrent writes, but no files, tests, or entry points. Start by locating the job implementations and configuration handling for those settings, then inspect existing validation tests. Done should be demonstrated by tests covering detection of configurations that violate the stated requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100