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

Lefty Leverenz commented on HIVE-11703:
---------------------------------------

[~pxiong], the wiki needs to cover all Hive versions so I've restored REGEXP 
and RLIKE to the non-reserved list with version information, and added version 
information in the reserved list.

* [DDL -- Non-reserved Keywords | 
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-Non-reservedKeywords]
* [DDL -- Reserved Keywords | 
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-ReservedKeywords]

> Make RegExp and RLike reserved keywords
> ---------------------------------------
>
>                 Key: HIVE-11703
>                 URL: https://issues.apache.org/jira/browse/HIVE-11703
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Pengcheng Xiong
>            Assignee: Pengcheng Xiong
>             Fix For: 2.0.0
>
>
> RegExp and RLike are treated as "precedenceEqualNegatableOperator" in Hive. 
> They actually come from MySQL. Both of them are not keywords in SQL2011. But 
> they are reserved keywords in MySQL. Making them reserved ones can eliminate 
> the current 14 ambiguities that we have in current Hive. If users still would 
> like to use them as identifiers/function names, users can "set 
> hive.support.sql11.reserved.keywords=false;"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to