[
https://issues.apache.org/jira/browse/HIVE-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181032#comment-14181032
]
Xuefu Zhang commented on HIVE-8561:
-----------------------------------
Hi @Na Yang, I took a brief look. With my limitted understanding of CBO code,
the patch looks fine. My only concern is that this seems expose some Hive's
internals to the outside world. If Hive make any changes on this, it might
inadvertantly break other applications. What's your thought on this? Is there a
different approach that achieves the same purpose, or has Hive exposed anything
similar to this?
> 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)
