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

Stefan Podkowinski commented on CASSANDRA-13371:
------------------------------------------------

Had to change the API for the startup check a bit and had to update the 
corresponding test for backporting...

||trunk||3.11||3.0||
|[branch|https://github.com/spodkowinski/cassandra/tree/CASSANDRA-13371-trunk]|[branch|https://github.com/spodkowinski/cassandra/tree/CASSANDRA-13371-3.11]|[branch|https://github.com/spodkowinski/cassandra/tree/CASSANDRA-13371-3.0]|
|[dtest|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/158]|[dtest|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/157]|[dtest|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/156]|
|[testall|https://circleci.com/gh/spodkowinski/cassandra/tree/CASSANDRA-13371-trunk]|[testall|https://circleci.com/gh/spodkowinski/cassandra/tree/CASSANDRA-13371-3.11]|[testall|https://circleci.com/gh/spodkowinski/cassandra/tree/CASSANDRA-13371-3.0]|



> Remove legacy auth tables support
> ---------------------------------
>
>                 Key: CASSANDRA-13371
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13371
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Auth
>            Reporter: Stefan Podkowinski
>            Assignee: Stefan Podkowinski
>              Labels: security
>             Fix For: 4.x
>
>
> Starting with Cassandra 3.0, we include support for converting pre 
> CASSANDRA-7653 user tables, until they will be dropped by the operator. 
> Converting e.g. permissions happens by simply copying all of them from 
> {{permissions}} -> {{role_permissions}}, until the {{permissions}} table has 
> been dropped.
> Upgrading to 4.0 will only be possible from 3.0 upwards, so I think it's safe 
> to assume that the new permissions table has already been populated, whether 
> the old table was dropped or not. Therefor I'd suggest to just get rid of the 
> legacy support.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to