Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
The default configuration files serve 2 purposes
1. Documenting available config parameters, and their default values.
2. Specifying default values for these parameters.
An xml file hidden inside a jar is not necessarily the best way to document parameters. This could be moved into the documentation itself.
Default values already exist in code for most parameters. There's no need to specify them in two places. We need to make sure defaults exist for all parameters before attempting this.
Having default configuration files just bloats job conf files; over 450 parameters, out of which <20 are likely job specific params. JobConf files end up being rather big, and the memory footprint of the conf object is large (>300KB last I checked).
Attachments
Issue Links
- is related to
-
HADOOP-7956 Remove duplicate definition of default config values
- Open