[
https://issues.apache.org/jira/browse/HIVE-8561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14187069#comment-14187069
]
Brock Noland commented on HIVE-8561:
------------------------------------
I am not familiar with the COB code so it's possible we want to take a
different approach. However, in principle I don't see an issue with the idea of
this change. Additionally, any API that we open to limited group of downstream
projects, such as Drill, should be marked with annotations. For example
{{LimitedPrivate("Apache Hive, Apache Drill (Incubating)")}} and then either
{{Unstable}} or {{Evolving}}.
https://github.com/apache/hive/blob/trunk/common/src/java/org/apache/hadoop/hive/common/classification/InterfaceAudience.java#L34
https://github.com/apache/hive/blob/trunk/common/src/java/org/apache/hadoop/hive/common/classification/InterfaceStability.java#L34
We should do that for any change which opens API's for Drill. Additionally, I
see we marked some members from java private to java public. As opposed to
doing that we should add getters for those member variables.
> 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)
