You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "He Yongqiang (JIRA)" <ji...@apache.org> on 2009/10/15 15:02:31 UTC

[jira] Updated: (HIVE-873) Better error messages for Hive cmdline

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

He Yongqiang updated HIVE-873:
------------------------------

    Attachment: hive-873-2009-10-15.patch

this patch has not been verified in a hadoop installation. no access to a cluster ...

> Better error messages for Hive cmdline
> --------------------------------------
>
>                 Key: HIVE-873
>                 URL: https://issues.apache.org/jira/browse/HIVE-873
>             Project: Hadoop Hive
>          Issue Type: New Feature
>            Reporter: Zheng Shao
>         Attachments: hive-873-2009-10-15.patch
>
>
> Currently, we are facing a lot of questions of Hive users because they cannot directly see what is the error causing the job to fail.
> We should expose that information to our user so that they can understand why their job failed easily.
> There are the 2 possible ways to get the error information:
> {code}
> RunningJob JobClient.submitJob();
> TaskCompletionEvent[] RunningJob.getTaskCompletionEvents()
> TaskCompletionEvent.getTaskTrackerHttp()
> {code}
> {code}
> TaskReport[] JobClient.getMapTaskReports();
> {code}
> We can edit ExecDriver.java and put that in after we submit a job.

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