hive-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edward Capriolo <>
Subject Re: Interpreting explain plan in hive
Date Fri, 23 Aug 2013 15:10:15 GMT
The only bad plan would be a plan that ends up producing the wrong result,
or throwing an exception. generally I look to see if there is a way to have
less map/reduce stages, the best plan is usually the one that does the job
in a single map reduce, or even better a single map only job.

On Fri, Aug 23, 2013 at 1:28 AM, pandees waran <> wrote:

> Hi,
> What are the key areas we need to check in the explain plan generated in
> Hive?
> I have checked the documentation, it's not detailed about the above
> question.
> I have similar kind of question asked in our forum, which is unanswered.
> In summary, how we can distinguish a good/bad plan ?
> Thanks for your help.
> --
> Thanks,
> Pandeeswaran

View raw message