Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 1 Jun 2011 18:13:47 +0000 (UTC)
From: "Eric Hassold (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: 
 <857584882.60498.1306952027805.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HIVE-1740) support NOT IN and NOT LIKE syntax
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HIVE-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13042336#comment-13042336 ] 

Eric Hassold commented on HIVE-1740:
------------------------------------

Moving IN in same rule caused '=' to no more have higher precedence than 'IN' operator (hence 1 = 1 IN (true, false) is parsed differently). Don't know how I missed this test failure, but will try to figure out how to keep support for NOT IN without breaking this.

> support NOT IN and NOT LIKE syntax
> ----------------------------------
>
>                 Key: HIVE-1740
>                 URL: https://issues.apache.org/jira/browse/HIVE-1740
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>    Affects Versions: 0.6.0
>            Reporter: John Sichi
>            Assignee: Eric Hassold
>         Attachments: HIVE-1740.1.patch.txt
>
>
> Hive should support standard SQL syntax
> x NOT LIKE p
> x NOT IN (...)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira