[
https://issues.apache.org/jira/browse/HADOOP-9300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615154#comment-13615154
]
Hadoop QA commented on HADOOP-9300:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12570034/HADOOP-9300-2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-tools/hadoop-streaming.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2370//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/2370//console
This message is automatically generated.
> Streaming fails to set output key class when reducer is java class
> ------------------------------------------------------------------
>
> Key: HADOOP-9300
> URL: https://issues.apache.org/jira/browse/HADOOP-9300
> Project: Hadoop Common
> Issue Type: Bug
> Components: tools
> Affects Versions: 2.0.2-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: HADOOP-9300-1.patch, HADOOP-9300-2.patch,
> HADOOP-9300-2.patch, HADOOP-9300-2.patch, HADOOP-9300.patch, HADOOP-9300.patch
>
>
> In an effort to avoid overwriting user configs (MAPREDUCE-1888), StreamJob
> doesn't set a job's output key/value classes unless they are specified in the
> streaming command line. If the configs aren't specified in either of these
> places, the streaming defaults (Text) no longer kick in, and the global
> default LongWritable is used.
> This can cause jobs/output writers that are expecting Text to fail.
--
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
