[
https://issues.apache.org/jira/browse/HIVE-12707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070298#comment-15070298
]
Pengcheng Xiong commented on HIVE-12707:
----------------------------------------
[~rajsaha], here is the story with timeline: Hive 0.14 was released based on
commits on Wed Nov 12 20:35:15 2014 (Since INTERVAL was not introduced yet, you
are free to use it as identifier). The flag
"hive.support.sql11.reserved.keywords" was introduced on Tue Mar 10 22:00:41
2015. (Since INTERVAL was not introduced yet, you are free to use it as
identifier whether you set the flag or not). "INTERVAL" was introduced on Thu
Mar 19 19:05:28 2015 (see HIVE-9792 : Support interval type in
expressions/predicates ), and they reserved it.... Sounds like the people who
checked in HIVE-9792 did not consider the backward compatibility of "interval".
So, if it really makes trouble for you, i can add it back to the list. But as
you know, we are planning to deprecate the flag in the next release or two.
> ParseException for column name 'INTERVAL', even set
> hive.support.sql11.reserved.keywords = false
> -------------------------------------------------------------------------------------------------
>
> Key: HIVE-12707
> URL: https://issues.apache.org/jira/browse/HIVE-12707
> Project: Hive
> Issue Type: Bug
> Affects Versions: 1.2.1
> Reporter: Rajit Saha
> Assignee: Pengcheng Xiong
> Fix For: 1.2.1
>
>
> Any column name INTERVAL is causing ParseException , even we set
> hive.support.sql11.reserved.keywords = false
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
