Sorry I haven't gotten a chance to look into this further.
I am fairly certain that it's a bug in Utilities.java which HIVE-4003
is going to fix. I am have been trying to reproduce the behavior
locally with trunk but so far, have been unsuccessful in doing so.
In any case, so it boils down to the shim you are using. Here is the
Shim for Hadoop 0.20.
Could you try setting mapred.job.tracker property in your
mapred-site.xml to your jobtracker and see if that fixes it?
Also, if you could provide me any information (your config, setup,
which queries fail, etc.) that could help me in reproducing the
problem on hive trunk would be greatly appreciated!
On Tue, Feb 19, 2013 at 1:08 AM, Marcin Cylke <[EMAIL PROTECTED]> wrote:
> On 14/02/13 08:27, Marcin Cylke wrote:
> > Actually I'm not using YARN, just the classic MR. Perhaps the setting is
> > somewhere in my configuration? My whole cluster is running MR1. Since
> > I'm running Cloudera cdh4.1 I'm starting hive with the following line:
> > HADOOP_MAPRED_HOME=/usr/lib/hadoop-0.20-mapreduce
> > HADOOP_HOME=/usr/lib/hadoop bin/hive
> > Is there anything else I can do to debug this issue? I'd like to
> > confirm, that in my situation Hive is not trying to use YARN.
> Could You suggest what to do next with this particular problem?