You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Arun C Murthy (JIRA)" <ji...@apache.org> on 2008/04/08 00:45:25 UTC
[jira] Resolved: (PIG-194) Exit code as logged in the task log does
not match actual one
[ https://issues.apache.org/jira/browse/PIG-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy resolved PIG-194.
-------------------------------
Resolution: Invalid
This is due to the fact that Xu was using a C++ binary compiled on a different machine from the machine on which it was actually being run... and hence it is undefined. We did test this with a perl script which had an exit code of 145 and it turned up right in the logs i.e. Pig-Streaming correctly preserved the exit-code of 145.
> Exit code as logged in the task log does not match actual one
> --------------------------------------------------------------
>
> Key: PIG-194
> URL: https://issues.apache.org/jira/browse/PIG-194
> Project: Pig
> Issue Type: Bug
> Reporter: Xu Zhang
> Assignee: Arun C Murthy
> Attachments: PigLoggingTest_fp_exception
>
>
> The actually exit code of PigLoggingTest_fp_exception when it is executed from the shell command line is 136 (run the executable and then get the exit code with "echo $?" on the command line). However, if a Pig script like the following is run, the task logs as shown in the task's UI incorrectly list the exit code as -127.
> {code}
> define X `PigLoggingTest_fp_exception 10 f` ship('./cplusplus/PigLoggingTest_fp_exception');
> A = load '/user/pig/tests/data/singlefile/studenttab10k' as (name, age, gpa);
> B = stream A through X;
> store B into 'results_n_30';
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.