[
https://issues.apache.org/jira/browse/HIVE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Yang updated HIVE-873:
---------------------------
Attachment: HIVE-873.1.patch
* Made modifications to patch, simplified code
Concerns:
* Why was rj.getTaskCompletionEvents() was checked repeatedly in a loop? I
removed the loop in the revision.
* Is there a better way to get the URL for the task info page?
conf.get("mapred.job.tracker", "local") has the wrong port # and
TaskCompletionEvent.getTaskTrackerHttp() doesn't return a usable address.
* Is the conf var hive.exec.fail.debug necessary? Should such info always be
displayed?
> 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
> Assignee: Paul Yang
> Attachments: hive-873-2009-10-15.patch, HIVE-873.1.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.