[
https://issues.apache.org/jira/browse/MAPREDUCE-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617301#comment-13617301
]
Hudson commented on MAPREDUCE-4994:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk #1358 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1358/])
MAPREDUCE-5006. Fix failing streaming tests due to MAPREDUCE-4994.
Contributed by Sandy Ryza. (Revision 1461541)
Result = FAILURE
tomwhite :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1461541
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapred/LocalClientProtocolProvider.java
*
/hadoop/common/trunk/hadoop-tools/hadoop-streaming/src/test/java/org/apache/hadoop/streaming/TestStreamReduceNone.java
*
/hadoop/common/trunk/hadoop-tools/hadoop-streaming/src/test/java/org/apache/hadoop/streaming/TestStreamXmlRecordReader.java
> -jt generic command line option does not work
> ---------------------------------------------
>
> Key: MAPREDUCE-4994
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4994
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Affects Versions: 2.0.2-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Fix For: 2.0.5-beta
>
> Attachments: MAPREDUCE-4994-1.patch, MAPREDUCE-4994-addendum-1.patch,
> MAPREDUCE-4994-addendum.patch, MAPREDUCE-4994.patch
>
>
> hadoop jar myjar.jar MyDriver -fs file:/// -jt local input.txt output/
> should run a job using the local file system and the local job runner.
> Instead it tries to connect to a jobtracker.
> hadoop jar myjar.jar MyDriver -fs file:/// -jt host:port input.txt output/
> does not use the given host/port
> This appears to be because Cluster#initialize, which loads the
> ClientProtocol, contains no special handling for mapred.job.tracker.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
