You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2013/08/15 19:25:47 UTC

[jira] [Commented] (OOZIE-1496) Oozie demo and streaming examples fails to run on Windows

    [ https://issues.apache.org/jira/browse/OOZIE-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741216#comment-13741216 ] 

Hadoop QA commented on OOZIE-1496:
----------------------------------

Testing JIRA OOZIE-1496

Cleaning local svn workspace

----------------------------

{color:red}-1{color} Patch failed to apply to head of branch

----------------------------
                
> Oozie demo and streaming examples fails to run on Windows
> ---------------------------------------------------------
>
>                 Key: OOZIE-1496
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1496
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Eugene Shevchuk
>            Assignee: Eugene Shevchuk
>         Attachments: fix.patch
>
>
> The mapreduce jobs which are run by streaming and demo oozie examples fails with following error:
> 	Caused by: java.io.IOException: Cannot run program "/bin/cat": CreateProcess error=2, The system cannot find the file specified
> 	Both have <streaming><mapper>/bin/cat</mapper><reducer>/usr/bin/wc</reducer></streaming> parameters in their workflow.xml. To fix this issue it's needed to have another mapper and reducer programms for Windows. As appropriate analogs on Windows can be "powershell -command "$input | Write-Host"" for mapper and "powershell -command "$input | Measure-Object -Word -Line -Character"" so it's not needed to rewrite any supporting Java code for this examples.
> 	That's why separated job.properties for Windows and Linux versions were created. Both contains additional parameters "streamingMapper" and "streamingReducer" whose values are commands for OS-specific mapper and reducer.

--
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