hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "rohithsharma (JIRA)" <>
Subject [jira] [Commented] (HIVE-2804) Task log retrieval fails on Hadoop 0.23
Date Wed, 20 Jun 2012 10:54:44 GMT


rohithsharma commented on HIVE-2804:

I also encountered the same problem with hive UDAF queries such as PERCENTILE and ASSERT_TRUE.
I have applied given patch and run these 2 queries. This patch fails throwing following excetiption.
Error during job, obtaining debugging information...
Examining task ID: task_1340014683209_0037_m_000000 (and more) from job job_1340014683209_0037
Exception in thread "Thread-26" java.lang.RuntimeException: Bad task log url
        at org.apache.hadoop.hive.ql.exec.errors.TaskLogProcessor.getStackTraces(
        at org.apache.hadoop.hive.ql.exec.JobDebugger.showJobFailDebugInfo(
Caused by:
        at org.apache.hadoop.hive.ql.exec.errors.TaskLogProcessor.getStackTraces(
        ... 3 more

Correct me if I am wrong ,
With my understanding problem is adding URI's into 'taskLogUrls', I feel we need null check
while adding URI into 'taskLogUrls'  because hadoop23shims returns null if the cluster is
MR2. This URI construction fails since null is passed as argument when TaskLogProcessor.getErrors()
or TaskLogProcessor.getStackTraces() is called and throws MalformedURLException.
> Task log retrieval fails on Hadoop 0.23
> ---------------------------------------
>                 Key: HIVE-2804
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Diagnosability, Query Processor, Security
>            Reporter: Carl Steinbach
>            Assignee: Zhenxiao Luo
>         Attachments: HIVE-2804.1.patch.txt, HIVE-2804.2.patch.txt, HIVE-2804.3.patch.txt,
HIVE-2804.4.patch.txt, HIVE-2804.5.patch.txt, HIVE-2804.5.patch.txt, HIVE-2804.6.patch.txt,
HIVE-2804.D3057.1.patch, HIVE-2804.D3057.2.patch, HIVE-2804.D3057.3.patch, HIVE-2804.D3219.1.patch,

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message