[
https://issues.apache.org/jira/browse/HIVE-12776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15087759#comment-15087759
]
Alan Gates commented on HIVE-12776:
-----------------------------------
Here's an example of what I'm worried about. A user is calling this interface
with Hive 1.2, and getting back an AST that maybe looks like A->B->C. In Hive
1.3 we make a language change, and the same syntax now produces a slightly
different AST. So after upgrading the user makes the same call with the same
input and gets A->B->D->C. I don't want to have to guarantee we won't cause
these kinds of issues. If we mark this clearly as not having backwards
compatibility guarantees then I'm perfectly fine with it.
> Add parse utility method for parsing any stand-alone HQL expression
> -------------------------------------------------------------------
>
> Key: HIVE-12776
> URL: https://issues.apache.org/jira/browse/HIVE-12776
> Project: Hive
> Issue Type: Improvement
> Reporter: Rajat Khandelwal
> Assignee: Rajat Khandelwal
> Attachments: HIVE-12776.01.patch, HIVE-12776.02.patch
>
>
> Extensions that use Hive QL as their standard language, will benefit from
> this.
> Apache Lens uses HQL as its language of choice. To support that, it depends
> on a fork of Hive, which has such code. I'm planning to port that to Apache
> Hive.
> Relevant commit:
> https://github.com/InMobi/hive/commit/7caea9ed1d269c1cd1d1326cb39c1db7e0bf2bba#diff-fb3acd67881ceb02e83c2e42cf70beef
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
