[
https://issues.apache.org/jira/browse/HIVE-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790027#comment-13790027
]
Ashutosh Chauhan edited comment on HIVE-5498 at 10/9/13 5:09 AM:
-----------------------------------------------------------------
This has many advantages:
* queries which metadata only optimizer currently targets can be run purely in
client without launching MR job. Currently it
launches MR job for it which is wasteful. So, it will be faster than its
current form.
* Since we won't be launching MR job we won't have to deal with bugs like
HIVE-3594 and HIVE-2955
* Than we can get rid of hacks like Utilites::getInputs() and
Utilities::setInputs()
* This will result in lesser code to maintain
* This can lay foundation for HIVE-4150
was (Author: ashutoshc):
This has many advantages:
* queries which metadata only optimizer currently targets can be run purely in
client without launching MR job. Currently it
launches MR job for it which is wasteful. So, it will be faster than its
current form.
* Since we won't be launching MR job we won't have to deal with bugs like
HIVE-3494 and HIVE-2955
* Than we can get rid of hacks like Utilites::getInputs() and
Utilities::setInputs()
* This will result in lesser code to maintain
* This can lay foundation for HIVE-4150
> Merge metadata only optimizer into simple fetch optimizer
> ---------------------------------------------------------
>
> Key: HIVE-5498
> URL: https://issues.apache.org/jira/browse/HIVE-5498
> Project: Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Ashutosh Chauhan
>
> Metadata only optimizer is currently written as physical optimizer. It can be
> merged into simple fetch optimizer where it will than become a logical
> optimizer.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
