[jira] [Updated] (CASSANDRA-21510) DROP USER statement reject unreserved keywords as names, breaking existing users after any new CQL keyword is added

["Maxim Muzafarov (Jira)" <ji...@apache.org>]

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

Maxim Muzafarov updated CASSANDRA-21510:
----------------------------------------
    Fix Version/s: 6.x
                   7.x

> DROP USER statement reject unreserved keywords as names, breaking existing users after any new CQL keyword is added
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21510
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21510
>             Project: Apache Cassandra
>          Issue Type: Bug
>            Reporter: Maxim Muzafarov
>            Assignee: Maxim Muzafarov
>            Priority: Normal
>             Fix For: 6.x, 7.x
>
>
> The username and identity grammar rules in Parser.g accept only IDENT | STRING_LITERAL:
> {code}
>   username
>       : IDENT
>       | STRING_LITERAL
>       | QUOTED_NAME { addRecognitionError(...) }
>       ;
> {code}
>   
> By contrast, the roleName rule additionally accepts unreserved_keyword. Consequently, whenever a word is promoted to an unreserved keyword in the lexer, tokenisation as IDENT stops. Any existing user or identity with that name silently loses access to the USER/IDENTITY statement forms after an upgrade.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org