Re: VolcanoPlanner vs HepPlanner

2015-10-07 Thread John Pullokkaran
e.org>" mailto:user@hive.apache.org>> Subject: Re: VolcanoPlanner vs HepPlanner my requirements. Internally, while enumerating the different join orders, it destroys "bad" query plans.

Re: VolcanoPlanner vs HepPlanner

2015-10-07 Thread Raajay Viswanathan
> Thanks > John > From: Raajay mailto:raaja...@gmail.com>> > Reply-To: "user@hive.apache.org <mailto:user@hive.apache.org>" > mailto:user@hive.apache.org>> > Date: Tuesday, October 6, 2015 at 2:06 PM > To: "user@hive.apache.org <mailto:user@h

Re: VolcanoPlanner vs HepPlanner

2015-10-07 Thread John Pullokkaran
pache.org>" mailto:user@hive.apache.org>> Date: Tuesday, October 6, 2015 at 2:06 PM To: "user@hive.apache.org<mailto:user@hive.apache.org>" mailto:user@hive.apache.org>> Subject: VolcanoPlanner vs HepPlanner Hello - While surfing the code in "apply&quo

VolcanoPlanner vs HepPlanner

2015-10-06 Thread Raajay
Hello - While surfing the code in "apply" function of CalcitePlannerAction (CalcitePlanner.java), I see that most rules are passed to a HepPlanner to arrive at the "least cost" operator tree. The HiveVolcanoPlanner although defined and initialized is never invoked to find the best operator tree.