浏览代码

MAPREDUCE-5713. InputFormat and JobConf JavaDoc Fixes (Chen He via jeagles)

git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/trunk@1577239 13f79535-47bb-0310-9956-ffa450edef68
Jonathan Turner Eagles 11 年之前
父节点
当前提交
2c6ce77c5a

+ 2 - 0
hadoop-mapreduce-project/CHANGES.txt

@@ -158,6 +158,8 @@ Release 2.5.0 - UNRELEASED
 
 
     MAPREDUCE-5765. Update hadoop-pipes examples README (Mit Desai via jeagles)
     MAPREDUCE-5765. Update hadoop-pipes examples README (Mit Desai via jeagles)
 
 
+    MAPREDUCE-5713. InputFormat and JobConf JavaDoc Fixes (Chen He via jeagles)
+
   OPTIMIZATIONS
   OPTIMIZATIONS
 
 
   BUG FIXES 
   BUG FIXES 

+ 1 - 1
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/InputFormat.java

@@ -54,7 +54,7 @@ import org.apache.hadoop.fs.FileSystem;
  * mapreduce.input.fileinputformat.split.minsize</a>.</p>
  * mapreduce.input.fileinputformat.split.minsize</a>.</p>
  * 
  * 
  * <p>Clearly, logical splits based on input-size is insufficient for many 
  * <p>Clearly, logical splits based on input-size is insufficient for many 
- * applications since record boundaries are to respected. In such cases, the
+ * applications since record boundaries are to be respected. In such cases, the
  * application has to also implement a {@link RecordReader} on whom lies the
  * application has to also implement a {@link RecordReader} on whom lies the
  * responsibilty to respect record-boundaries and present a record-oriented
  * responsibilty to respect record-boundaries and present a record-oriented
  * view of the logical <code>InputSplit</code> to the individual task.
  * view of the logical <code>InputSplit</code> to the individual task.

+ 4 - 3
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/JobConf.java

@@ -66,9 +66,10 @@ import org.apache.log4j.Level;
  *   </li>
  *   </li>
  *   <li>
  *   <li>
  *   While some job parameters are straight-forward to set 
  *   While some job parameters are straight-forward to set 
- *   (e.g. {@link #setNumReduceTasks(int)}), some parameters interact subtly 
- *   rest of the framework and/or job-configuration and is relatively more 
- *   complex for the user to control finely (e.g. {@link #setNumMapTasks(int)}).
+ *   (e.g. {@link #setNumReduceTasks(int)}), some parameters interact subtly
+ *   with the rest of the framework and/or job-configuration and is relatively
+ *   more complex for the user to control finely
+ *   (e.g. {@link #setNumMapTasks(int)}).
  *   </li>
  *   </li>
  * </ol></p>
  * </ol></p>
  * 
  *