[
https://issues.apache.org/jira/browse/HIVE-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183700#comment-14183700
]
Na Yang commented on HIVE-8561:
-------------------------------
Hi [~xuefuz] and [~jpullokkaran], thank you both very much for reviewing this
patch. I understand your concern of adding a public API to expose Optiq Op tree
to outside world. To address the risk of calling this API outside, I added
warning on the Java doc. It is the caller's responsibility to follow the hive
side change if they want to use this API to get the Hive's Optiq Op tree.
[~jpullokkaran], your understanding is correct. The goal of this patch is to
use Hive for query parsing and use Drill as the execution engine. Since hive
has already generated the Optiq Op tree, it is possible for drill to use it
directly.
Thanks & Regards,
Na
> 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.2.patch, 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)
