Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hive-dev@hadoop.apache.org
Message-ID: <1343451876.1255672591351.JavaMail.jira@brutus>
Date: Thu, 15 Oct 2009 22:56:31 -0700 (PDT)
From: "Zheng Shao (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Subject: [jira] Commented: (HIVE-873) Better error messages for Hive cmdline
In-Reply-To: <1757741686.1255395692134.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Zheng Shao commented on HIVE-873:
---------------------------------

hive-873-2009-10-15.patch: I tried it. It does not work now.


> 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.