Thanks. mapred.reduce.tasks and hive.exec.reducers.max seem to have fixed the
problem. It is now saturating the cluster and running the query super fast.
Excellent!
On Sep 30, 2013, at 12:28 , Sean Busbey wrote:
> Hey Keith,
>
> It sounds like you should tweak the settings for how Hive hand
Hey Keith,
It sounds like you should tweak the settings for how Hive handles query
execution[1]:
1) Tune the guessed number of reducers based on input size
= hive.exec.reducers.bytes.per.reducer
Defaults to 1G. Based on your description, it sounds like this is probably
still at default.
In thi
