You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/01/29 19:56:34 UTC

[jira] [Commented] (DRILL-2116) Add non-reserved keywords to non-reserved keyword list in parser

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

Julian Hyde commented on DRILL-2116:
------------------------------------

The following statement will be ambiguous if you make LEFT non-reserved: {code}select * from t1 left join t2 rite on left.x = rite.y{code}

> Add non-reserved keywords to non-reserved keyword list in parser
> ----------------------------------------------------------------
>
>                 Key: DRILL-2116
>                 URL: https://issues.apache.org/jira/browse/DRILL-2116
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: SQL Parser
>            Reporter: Jacques Nadeau
>            Assignee: Aman Sinha
>
> There are a number of keywords in Drill that shouldn't be considered reserved when parsing.  Calcite allows us to customize the list of un-reserved keywords and we should update the list to allow more words.  Things that I've run across include value, user, left, etc.  
> This is a very common usability problem.



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