[
https://issues.apache.org/jira/browse/CASSANDRA-10904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe resolved CASSANDRA-10904.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.3
3.2
2.2.5
I've added the upgrade instructions to NEWS.txt in
{{df49cec1caeaa710f0e32516b635b60426da6cd9}}.
For reference:
bq. what are the "legacy tables" that should be dropped.
>From the {{system_auth}} keyspace, the tables to drop are {{users}},
>{{credentials}} and {{permissions}}. Actually, it's only essential to drop
>{{credentials}} and {{permissions}}, but {{users}} is unused once the other
>two are dropped.
bq. how to verify if the schema upgrade is successful.
You could manually compare the data in the the old tables with that in the new
{{roles}} and {{role_permissions}} tables, but the schema is obviously
different so it isn't just a simple 1:1 mapping. A more straightforward way
would be to simply restart a node and monitor its {{system.log}}. As long as
the legacy tables haven't been dropped, the node will re-run the data
conversion at startup and report its outcome. You should look for the following
lines in the log:
{noformat}
INFO [OptionalTasks:1] CassandraRoleManager.java:410 - Converting legacy users
INFO [OptionalTasks:1] CassandraRoleManager.java:420 - Completed conversion of
legacy users
INFO [OptionalTasks:1] CassandraRoleManager.java:425 - Migrating legacy
credentials data to new system table
INFO [OptionalTasks:1] CassandraRoleManager.java:438 - Completed conversion of
legacy credentials
INFO [OptionalTasks:1] CassandraAuthorizer.java:396 - Converting legacy
permissions data
INFO [OptionalTasks:1] CassandraAuthorizer.java:435 - Completed conversion of
legacy permissions
{noformat}
> Add upgrade procedure related to new role based access control in NEWS.txt
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-10904
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10904
> Project: Cassandra
> Issue Type: Task
> Components: Documentation and Website
> Reporter: Reynald Bourtembourg
> Labels: documentation
> Fix For: 2.2.5, 3.2, 3.0.3
>
>
> The upgrade procedure related to new role based access control feature in
> Cassandra 2.2 is not documented in NEWS.txt file.
> The upgrade procedure is described in this blog post:
> http://www.datastax.com/dev/blog/role-based-access-control-in-cassandra
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
