[
https://issues.apache.org/jira/browse/HIVE-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183151#comment-14183151
]
Laljo John Pullokkaran commented on HIVE-8561:
----------------------------------------------
Na Yang,
If i understand correctly, goal of this patch is to use Hive for query
parsing, resolving, cost based optimization and use Drill as the execution
engine. If my guess is right this patch makes Hive's Optiq Op tree a public
interface. The Hive's Optiq Op tree is not meant to be a public interface and
it would go through many changes as we add more to CBO & support for more
operators.
Why can't Drill be plugged in as another execution engine just like MR, TEZ,
Spark?
> Expose Hive optiq operator tree to be able to support other sql on hadoop
> query engines
> ---------------------------------------------------------------------------------------
>
> Key: HIVE-8561
> URL: https://issues.apache.org/jira/browse/HIVE-8561
> Project: Hive
> Issue Type: Task
> Components: CBO
> Affects Versions: 0.14.0
> Reporter: Na Yang
> Assignee: Na Yang
> Attachments: HIVE-8561.patch
>
>
> Hive-0.14 added cost based optimization and optiq operator tree is created
> for select queries. However, the optiq operator tree is not visible from
> outside and hard to be used by other Sql on Hadoop query engine such as
> apache Drill. To be able to allow drill to access the hive optiq operator
> tree, we need to add a public api to return the hive optiq operator tree.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
