Explore naming properties based on functionality instead of where the functionality runs
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 487
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 13
Description
Some properties in Accumulo related to functionality like compactions are named based on where that functionality runs. For example compactions used to all run in the tablet server, so lots of compaction related properties had a tserver prefix. In the elasticity branch where functionality is running is moving around. It may be better to name properties based on functionality instead of where the functionality runs. For example have a top level `compaction` prefix for compaction related properties instead using the `tserver` prefix.
Need to perform a survey of properties and see how many could be adjusted.
Contributor guide
Research direction
Start by surveying Accumulo's property definitions and usages, focusing on compaction-related properties with a tserver prefix and their movement in the elasticity branch. Identify which names are tied to execution location rather than functionality. Done means the affected properties and the scope of any naming changes are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases, distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100