You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Venky Iyer (JIRA)" <ji...@apache.org> on 2009/03/11 01:34:50 UTC

[jira] Commented: (HIVE-251) Failures in Transform don't stop the job

    [ https://issues.apache.org/jira/browse/HIVE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680708#action_12680708 ] 

Venky Iyer commented on HIVE-251:
---------------------------------

I believe this has to do with cases where the (streaming) script reads in all of its input from stdin and _then_ fails. Scripts that fail before reading in all their input are correctly marked as having failed. 

> Failures in Transform don't stop the job
> ----------------------------------------
>
>                 Key: HIVE-251
>                 URL: https://issues.apache.org/jira/browse/HIVE-251
>             Project: Hadoop Hive
>          Issue Type: Bug
>          Components: Serializers/Deserializers
>            Reporter: S. Alex Smith
>            Priority: Blocker
>
> If the program executed via a SELECT TRANSFORM() USING 'foo' exits with a non-zero exit status, Hive proceeds as if nothing bad happened.  The main way that the user knows something bad has happened is if the user checks the logs (probably because he got no output).  This is doubly bad if the program only fails part of the time (say, on certain inputs) since the job will still produce output and thus the problem will likely go undetected.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.