You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/07/26 00:13:34 UTC
[jira] [Commented] (OOZIE-862) In Map-only Streaming
(reducer=NONE), oozie runs reducer along with mapper(s).
[ https://issues.apache.org/jira/browse/OOZIE-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422673#comment-13422673 ]
Alejandro Abdelnur commented on OOZIE-862:
------------------------------------------
the NONE option in the command line of streaming is for backwards compatibility. And the recommended way is to set 'mapred.job.reduces=0'. Does this currently work? if so i think we should close the JIRA as invalid.
> In Map-only Streaming (reducer=NONE), oozie runs reducer along with mapper(s).
> ------------------------------------------------------------------------------
>
> Key: OOZIE-862
> URL: https://issues.apache.org/jira/browse/OOZIE-862
> Project: Oozie
> Issue Type: Improvement
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Priority: Minor
> Attachments: OOZIE-862-v2.patch, OOZIE-862.patch
>
>
> Oozie runs map-only streaming job with reducer, which is not intended.
> It always creates reducer when I give any of the following in *workflow.xml*
> --------------------------------------------
> <streaming>
> <mapper>mule_perm.pl</mapper>
> <reducer>NONE</reducer>
> </streaming>
> --------------------------------------------
> Or
> --------------------------------------------
> <streaming>
> <mapper>mule_perm.pl</mapper>
> </streaming>
> --------------------------------------------
> No reducer is created only when, I give following in *workflow.xml* as
> configuration. (which is not intuitive/matching with hadoop jar streaming
> command).
> ------------------------------------------
> <configuration>
> <property>
> <name>mapred.reduce.tasks</name>
> <value>0</value>
> </property>
> ...
> ------------------------------------------
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira