[ 
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.0-alpha2
                         7.0
                             (was: 6.x)
                             (was: 7.x)
          Since Version: 6.0-alpha1
    Source Control Link: 
https://github.com/apache/cassandra/commit/c4c3048b13ca446966d79cce6499b8f826ac61a0
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

[~dnk] thank you for review!
Merged to 6.x and 7.x branches.

> 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
>          Components: CQL/Interpreter
>            Reporter: Maxim Muzafarov
>            Assignee: Maxim Muzafarov
>            Priority: Normal
>             Fix For: 6.0-alpha2, 7.0
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to