hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Thusoo (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HIVE-251) Failures in Transform don't stop the job
Date Tue, 17 Mar 2009 22:43:50 GMT

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

Ashish Thusoo updated HIVE-251:
-------------------------------

    Attachment: patch-251_1.txt

uploading a new patch as there was a non determinism in an existing test. Please review this
again.

> 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
>    Affects Versions: 0.2.0
>            Reporter: S. Alex Smith
>            Assignee: Ashish Thusoo
>            Priority: Blocker
>             Fix For: 0.3.0
>
>         Attachments: patch-251.txt, patch-251_1.txt
>
>
> 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.


Mime
View raw message