Context Object for initialization
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 487
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 13
Description
I am not sure if this should be done or not so I am opening an issue for discussion/feedback/design ideas.
InitializeContext would be the object to represent the special internal state of Accumulo, before/during its initialization. This became troublesome when I started touching the VolumeManager.
server/base/src/main/java/org/apache/accumulo/server/InitializeContext.java
public class InitializeContext extends ServerContext {
private VolumeManager fs;public InitializeContext(SiteConfiguration siteConf, Configuration hadoopConf) throws IOException {
super(siteConf, hadoopConf);
fs = VolumeManagerImpl.get(siteConf, hadoopConf);
}
Most of the changes would be with server/base/src/main/java/org/apache/accumulo/server/init/Initialize.java. I was thinking maybe this context object could have a simple boolean state to check whether Accumulo has been initialized or not. Thoughts?
Contributor guide
Research direction
Read server/base/src/main/java/org/apache/accumulo/server/InitializeContext.java and server/base/src/main/java/org/apache/accumulo/server/init/Initialize.java first. Review the unresolved discussion about representing initialization state and VolumeManager access; done requires an agreed design and implementation scope, which this issue currently does not define.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100