Migrations access can be optimized
Open
enhancement
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 487
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 13
Description
**Is your feature request related to a problem? Please describe.**
#5416 changed how migrations are stored and accessed. How they are currently accessed can be optimized.
**Describe the solution you'd like**
See suggestions in link below
Originally posted by @keith-turner: https://github.com/apache/accumulo/pull/5416#discussion_r2067430572
Contributor guide
Research direction
Start by reviewing issue #5416 and the migration storage and access changes it introduced. Then read the suggestions in the linked pull-request discussion to determine the intended optimization; done means implementing an agreed approach and verifying that migration access still works correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100