[jira] [Updated] (CASSANDRA-4186) CQL3: make some keywords unreserved

["Sylvain Lebresne (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne updated CASSANDRA-4186:
----------------------------------------

    Attachment: 0001-Add-unreserved-words.txt

Patch attached to have some keywords not reserved. I'll admit I've use the list of reserved/non-reserver keywords of postgreSQL as inspiration for which to reserve or not, but I'm open to a few changes if someone has good reason for it.

The patch also adds the list of native types directly in the grammar so as to only parse those (or a string for custom ones) and to make them case insensitive. They are not reserved. 
                
> CQL3: make some keywords unreserved
> -----------------------------------
>
>                 Key: CASSANDRA-4186
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4186
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 1.1.0
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>              Labels: cql3
>             Fix For: 1.1.1
>
>         Attachments: 0001-Add-unreserved-words.txt
>
>
> CQL has quite a few keywords. Currently all of them are reserved, but this is not always necessary. PostreSQL for instance distinguish between reserved keywords and non-reserved ones, and allow things like {{key}}, {{timestamp}} or {{type}} as identifiers. I suggest we do the same as convenience for the user.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira