Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Not A Problem
-
0.89-fb
-
None
-
None
Description
Over time, features people work get buried in the large heap of config parameters that we have. This task is to find and document all the config parameters in hbase and tag them. This should be automated so that we can run it every now and then and find out the lost configs.
Ideas on how these can be found :
1. Look for Configuration objects and identify where we are setting values.
2. Identify constants/strings that are the parameter names.
3. Identify the constants that are default values.
4. Identify where in the code they are present and tag them appropriately, for example if a constant is being read in a bunch of places like HRegionServer.class, HRegion.class, we can tag it with HRegionServer and HRegion. We can go a bit further and subtag them with the functions they are displayed in.
5. Obtain the comments around the parameter name constants when they are defined.
A few pointers to traversing the java source tree :
http://stackoverflow.com/questions/2183488/traversing-through-the-ast-node
http://www.vogella.com/tutorials/EclipseJDT/article.html