Affects Version/s: 0.18.0
Fix Version/s: None
If we had different interfaces for the different configuration names as a set of constants, instead of using inline strings
1. we could detect naming inconsistencies (and spelling errors) faster
2. it would be easier for other applications (downstream, such as HBase) or tools that set the parameters) to actually set the parameters.
3. It would be eaiser to change the names, if desired.
4. it would be easy to detect all usages within a single project.
The interface classes could be hand generated (turn existing references into constants), or they could be auto-generated from an XML template. The latter would work if the default values included a definition of every possible supported attribute, somehow grouped so that jobconf values could be kept separate from dfs constants.
There is an incomplete hand-generated example at