Hive launching next job in sequence - even if preceding one fails

[Shrijeet Paliwal <sh...@rocketfuel.com>]

Hi,

Hive Version: 0.5
Hadoop Version: 0.20
Job submitted through: Hive Command Line

I noticed this today after upgrading to hive 0.5 (we moved up from 0.4 very
recently). A complex query is made of four map reduce jobs as indicated in
the log entries below. The first job fails, but the second in chain still
gets launched and hive
exits with error only after running all four jobs. Shouldn't this be
happening (hive exiting with error) after first failure itself? Do I need
to turn some knobs to make this happen?

10/09/02 13:07:42 INFO utils.FileTools$StreamEater: Total MapReduce jobs = 4
10/09/02 13:07:42 INFO utils.FileTools$StreamEater:
Launching Job 1 out of 4
Number of reduce tasks not specified. Defaulting to jobconf value of: 5
In order to change the average load for a reducer (in bytes):
 set hive.exec.reducers.bytes.per.reducer=<number>
In order to limit the maximum number of reducers:
 set hive.exec.reducers.max=<number>
In order to set a constant number of reducers:
 set mapred.reduce.tasks=<number>

10/09/02 13:07:51 INFO utils.FileTools$StreamEater: Starting Job =
job_201008231633_8124, Tracking URL =
http://hadoop-master.pww.rfiserve.net:50030/jobdetails.jsp?jobid=job_201008231633_8124
Kill Command = /usr/lib/hadoop-0.20/bin/hadoop job
 -Dmapred.job.tracker=hdfs://hadoop-master.pww.rfiserve.net:8021 -kill
job_201008231633_8124
.
.
.
.
10/09/02 13:38:35 INFO utils.FileTools$StreamEater: Ended Job =
job_201008231633_8124 with errors
10/09/02 13:38:35 INFO utils.FileTools$StreamEater:
Failed tasks with most(5) failures :
10/09/02 13:38:35 INFO utils.FileTools$StreamEater:
Task URL:
http://hadoop-master.pww.rfiserve.net:50030/taskdetails.jsp?jobid=job_201008231633_8124&tipid=task_201008231633_8124_m_003695

Launching Job 2 out of 4 *<-- WHY?*

-Shrijeet