[
https://issues.apache.org/jira/browse/DRILL-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939057#comment-14939057
]
Julian Hyde commented on DRILL-3875:
------------------------------------
You can't make JOIN non-reserved. If you do, people will be entitled to expect
the parser to be able to handle queries like {code}select * from join join join
join join using (join){code}. (Here 'join' is a table, table alias and column
name.)
If you get rid of reserved words, the parser cannot make progress if it sees an
identifier that might also be part of the "structure" of the query.
I would strongly recommend against making SQL standard reserved words
non-reserved.
> Reserved words in option names
> ------------------------------
>
> Key: DRILL-3875
> URL: https://issues.apache.org/jira/browse/DRILL-3875
> Project: Apache Drill
> Issue Type: Improvement
> Components: Execution - Flow
> Reporter: Sudheesh Katkam
>
> Either remove keywords from option names or create a list of non-reserved
> keywords.
> The list of keywords that we need to add to the non-reserved list: ["EXEC",
> "JOIN", "WINDOW", "LARGE", "PARTITION", "OLD", "COLUMN"].
> See comments [here|https://github.com/apache/drill/pull/159].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
