hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Namit Jain <nj...@fb.com>
Subject Re: Transform.java Vs. PhysicalPlanResolver.java
Date Wed, 28 Nov 2012 04:06:57 GMT

Optimizations in the Transform take the operator tree and transform that
into a new operator tree.
Then the operator tree is broken into various tasks.
Physical optimizer takes a task and optimizes/changes the task.

Both these optimizations are done at compile time.

There is nothing like a runtime optimization right now, the plan does not
change dynamically.



On 11/28/12 8:54 AM, "Mahsa Mofidpoor" <mofidpoor@gmail.com> wrote:

>Hello,
>
>1) Does Hive consider a clear-cut distinction between compile-time
>optimization and run-time optimization?
>2) Does anybody know the difference between the optimizations implementing
>the Transform and the ones implementing the PhysicalPlanResolver? Why such
>optimizations are they in separate packages?
>
>Thanks and Regards,
>Mahsa


Mime
View raw message