[
https://issues.apache.org/jira/browse/HIVE-701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584073#comment-13584073
]
Samuel Yuan commented on HIVE-701:
----------------------------------
Taking out DISTINCT and ALL takes the lines of warnings down from about 2900 to
around 2300. We were originally at around 1000. I can try taking out more
keywords to reduce the ambiguity.
By the way, what is the concern about the ambiguity? There is no impact to the
user, and I don't think there's much of a performance hit. Is it just that the
warnings are clogging up the build log, or is there something else?
> lots of reserved keywords in hive
> ---------------------------------
>
> Key: HIVE-701
> URL: https://issues.apache.org/jira/browse/HIVE-701
> Project: Hive
> Issue Type: New Feature
> Components: Query Processor
> Reporter: Namit Jain
> Assignee: Samuel Yuan
> Fix For: 0.11.0
>
> Attachments: HIVE-701.1.patch.txt, HIVE-701.2.patch.txt,
> HIVE-701.D8397.1.patch, HIVE-701.HIVE-701.D8397.2.patch,
> HIVE-701.HIVE-701.D8397.3.patch
>
>
> There is a problem if we want to use some reserved keywords:
> for example, creating a function of name left/right ? left/right is already a
> reserved keyword.
> The other way around should also be possible - if we want to add a 'show
> tables status' and some applications already use status as a column name,
> they should not break
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
