119119/**
120120 * Provides access to configuration parameters.
121121 *
122- * <h3 id="Resources">Resources</h3 >
122+ * <h2 id="Resources">Resources</h2 >
123123 *
124124 * <p>Configurations are specified by resources. A resource contains a set of
125125 * name/value pairs as XML data. Each resource is named by either a
130130 *
131131 * <p>Unless explicitly turned off, Hadoop by default specifies two
132132 * resources, loaded in-order from the classpath: <ol>
133- * <li><tt >
133+ * <li><code >
134134 * <a href="{@docRoot}/../hadoop-project-dist/hadoop-common/core-default.xml">
135- * core-default.xml</a></tt >: Read-only defaults for hadoop.</li>
136- * <li><tt >core-site.xml</tt >: Site-specific configuration for a given hadoop
135+ * core-default.xml</a></code >: Read-only defaults for hadoop.</li>
136+ * <li><code >core-site.xml</code >: Site-specific configuration for a given hadoop
137137 * installation.</li>
138138 * </ol>
139139 * Applications may add additional resources, which are loaded
140140 * subsequent to these resources in the order they are added.
141141 *
142- * <h4 id="FinalParams">Final Parameters</h4 >
142+ * <h3 id="FinalParams">Final Parameters</h3 >
143143 *
144144 * <p>Configuration parameters may be declared <i>final</i>.
145145 * Once a resource declares a value final, no subsequently-loaded
153153 * </property></code></pre>
154154 *
155155 * Administrators typically define parameters as final in
156- * <tt >core-site.xml</tt > for values that user applications may not alter.
156+ * <code >core-site.xml</code > for values that user applications may not alter.
157157 *
158- * <h4 id="VariableExpansion">Variable Expansion</h4 >
158+ * <h3 id="VariableExpansion">Variable Expansion</h3 >
159159 *
160160 * <p>Value strings are first processed for <i>variable expansion</i>. The
161161 * available properties are:<ol>
185185 * </property>
186186 * </code></pre>
187187 *
188- * <p>When <tt >conf.get("tempdir")</tt > is called, then <tt >${<i>basedir</i>}</tt >
188+ * <p>When <code >conf.get("tempdir")</code > is called, then <code >${<i>basedir</i>}</code >
189189 * will be resolved to another property in this Configuration, while
190- * <tt >${<i>user.name</i>}</tt > would then ordinarily be resolved to the value
190+ * <code >${<i>user.name</i>}</code > would then ordinarily be resolved to the value
191191 * of the System property with that name.
192- * <p>When <tt >conf.get("otherdir")</tt > is called, then <tt >${<i>env.BASE_DIR</i>}</tt >
193- * will be resolved to the value of the <tt >${<i>BASE_DIR</i>}</tt > environment variable.
194- * It supports <tt >${<i>env.NAME:-default</i>}</tt > and <tt >${<i>env.NAME-default</i>}</tt > notations.
195- * The former is resolved to "default" if <tt >${<i>NAME</i>}</tt > environment variable is undefined
192+ * <p>When <code >conf.get("otherdir")</code > is called, then <code >${<i>env.BASE_DIR</i>}</code >
193+ * will be resolved to the value of the <code >${<i>BASE_DIR</i>}</code > environment variable.
194+ * It supports <code >${<i>env.NAME:-default</i>}</code > and <code >${<i>env.NAME-default</i>}</code > notations.
195+ * The former is resolved to "default" if <code >${<i>NAME</i>}</code > environment variable is undefined
196196 * or its value is empty.
197- * The latter behaves the same way only if <tt >${<i>NAME</i>}</tt > is undefined.
197+ * The latter behaves the same way only if <code >${<i>NAME</i>}</code > is undefined.
198198 * <p>By default, warnings will be given to any deprecated configuration
199199 * parameters and these are suppressible by configuring
200- * <tt >log4j.logger.org.apache.hadoop.conf.Configuration.deprecation</tt > in
200+ * <code >log4j.logger.org.apache.hadoop.conf.Configuration.deprecation</code > in
201201 * log4j.properties file.
202202 *
203- * <h4 id="Tags">Tags</h4 >
203+ * <h3 id="Tags">Tags</h3 >
204204 *
205205 * <p>Optionally we can tag related properties together by using tag
206206 * attributes. System tags are defined by hadoop.tags.system property. Users
220220 * <tag>HDFS,SECURITY</tag>
221221 * </property>
222222 * </code></pre>
223- * <p> Properties marked with tags can be retrieved with <tt >conf
224- * .getAllPropertiesByTag("HDFS")</tt > or <tt >conf.getAllPropertiesByTags
225- * (Arrays.asList("YARN","SECURITY"))</tt >.</p>
223+ * <p> Properties marked with tags can be retrieved with <code >conf
224+ * .getAllPropertiesByTag("HDFS")</code > or <code >conf.getAllPropertiesByTags
225+ * (Arrays.asList("YARN","SECURITY"))</code >.</p>
226226 */
227227@ InterfaceAudience .Public
228228@ InterfaceStability .Stable
@@ -576,7 +576,7 @@ public static void addDeprecations(DeprecationDelta[] deltas) {
576576 * It does not override any existing entries in the deprecation map.
577577 * This is to be used only by the developers in order to add deprecation of
578578 * keys, and attempts to call this method after loading resources once,
579- * would lead to <tt >UnsupportedOperationException</tt >
579+ * would lead to <code >UnsupportedOperationException</code >
580580 *
581581 * If a key is deprecated in favor of multiple keys, they are all treated as
582582 * aliases of each other, and setting any one of them resets all the others
@@ -604,7 +604,7 @@ public static void addDeprecation(String key, String[] newKeys,
604604 * It does not override any existing entries in the deprecation map.
605605 * This is to be used only by the developers in order to add deprecation of
606606 * keys, and attempts to call this method after loading resources once,
607- * would lead to <tt >UnsupportedOperationException</tt >
607+ * would lead to <code >UnsupportedOperationException</code >
608608 *
609609 * If you have multiple deprecation entries to add, it is more efficient to
610610 * use #addDeprecations(DeprecationDelta[] deltas) instead.
@@ -624,7 +624,7 @@ public static void addDeprecation(String key, String newKey,
624624 * It does not override any existing entries in the deprecation map.
625625 * This is to be used only by the developers in order to add deprecation of
626626 * keys, and attempts to call this method after loading resources once,
627- * would lead to <tt >UnsupportedOperationException</tt >
627+ * would lead to <code >UnsupportedOperationException</code >
628628 *
629629 * If a key is deprecated in favor of multiple keys, they are all treated as
630630 * aliases of each other, and setting any one of them resets all the others
@@ -648,7 +648,7 @@ public static void addDeprecation(String key, String[] newKeys) {
648648 * It does not override any existing entries in the deprecation map.
649649 * This is to be used only by the developers in order to add deprecation of
650650 * keys, and attempts to call this method after loading resources once,
651- * would lead to <tt >UnsupportedOperationException</tt >
651+ * would lead to <code >UnsupportedOperationException</code >
652652 *
653653 * If you have multiple deprecation entries to add, it is more efficient to
654654 * use #addDeprecations(DeprecationDelta[] deltas) instead.
0 commit comments