You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 07:21:09 UTC

[jira] [Created] (OOZIE-351) GH-566: If Java Main exit code !=0, LauncherMapper should the exit code as the error code

GH-566: If Java Main exit code !=0, LauncherMapper should the exit code as the error code
-----------------------------------------------------------------------------------------

                 Key: OOZIE-351
                 URL: https://issues.apache.org/jira/browse/OOZIE-351
             Project: Oozie
          Issue Type: Bug
            Reporter: Hadoop QA


Currently the wf:errorCode(NODE) is fixed to some internal Oozie error codes.

Because of this, a WF app cannot decide what to do base on the Java Main exit code.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (OOZIE-351) GH-566: If Java Main exit code !=0, LauncherMapper should the exit code as the error code

Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/jira/browse/OOZIE-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Shaposhnik closed OOZIE-351.
----------------------------------

    Resolution: Fixed

> GH-566: If Java Main exit code !=0, LauncherMapper should the exit code as the error code
> -----------------------------------------------------------------------------------------
>
>                 Key: OOZIE-351
>                 URL: https://issues.apache.org/jira/browse/OOZIE-351
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Hadoop QA
>
> Currently the wf:errorCode(NODE) is fixed to some internal Oozie error codes.
> Because of this, a WF app cannot decide what to do base on the Java Main exit code.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira