[
https://issues.apache.org/jira/browse/HIVE-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041913#comment-13041913
]
Eric Hassold commented on HIVE-1740:
------------------------------------
The IN operator is turned into a different AST, which root is TOK_FUNCTION
(that is, TOK_FUNCTION^ KW_IN ...), and that's probably why KW_IN wasn't part
of precedenceEqualExpression either. If putting KW_IN into
precedenceEqualNegatableOperator, this would require testing operator after ->
to generate this different AST when operator is KW_IN, which IMHO would end up
in a more complex and less readable change. Does it make sense?
> 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
