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. Is this done for performance reasons only ?
Are both these planner inter-changeable for applying CBO to hive queries ?

Thanks
Raajay

Reply via email to