Align table services config names
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
To simplify the configuration, it would be good to align on how we call the configs for table services: auto, async, inline.
summary from [~alexey.kudinkin]
1. We should keep “auto” config to be able to flip b/w whether we perform any table-services at all (true — we do automatically, false — we disable them)
2. We introduce 1 config defining “mode” of executing the Service: either “inline” or “async”
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-3415
- Type: Improvement
- Epic: https://issues.apache.org/jira/browse/HUDI-1239
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the table-services configuration definitions and all usages of the auto, async, and inline names; verify how enabling or disabling services is represented and how execution mode is selected. Done means the configuration consistently supports the auto toggle and the inline/async mode without conflicting names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100