[
https://issues.apache.org/jira/browse/CASSANDRA-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102887#comment-16102887
]
Stefan Podkowinski commented on CASSANDRA-13371:
------------------------------------------------
I've rebased the patch and added the startup check, test and NEWS.txt of yours.
* [branch|https://github.com/spodkowinski/cassandra/tree/CASSANDRA-13371]
* [test-all|https://circleci.com/gh/spodkowinski/cassandra/tree/CASSANDRA-13371]
*
[dtest|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/150/]
Btw, there's also CASSANDRA-13662 if you're interested in further cleanup for
trunk.
> Remove legacy auth tables support
> ---------------------------------
>
> Key: CASSANDRA-13371
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13371
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Stefan Podkowinski
> Assignee: Stefan Podkowinski
> 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]
