The M/R job that's generated for the nohup case is very different from
the non-nohup case: It has only 1 map task and it ran to completion very
The M/R job for non-nohup case has many map tasks and it took a while to
run (to generate the correct result).
From: Raghu Murthy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 20, 2009 15:42
To: [EMAIL PROTECTED]
Subject: Re: Nohupping the hive CLI causes wrong behavior
Did you check that nohup.out didn't have the result?
On 8/20/09 3:21 PM, "Steven Wong" <[EMAIL PROTECTED]> wrote:
> I get correct result if I run: hive -e "select count(1) from blah
> But I get no result if I run: nohup hive -e "select count(1) from blah
> In both cases, hive exited with 0 (success). Very strange.
> Hive is from trunk revision 795559.