You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Kai Wang (JIRA)" <ji...@apache.org> on 2015/12/18 15:12:46 UTC

[jira] [Commented] (CASSANDRA-10904) Add upgrade procedure related to new role based access control in NEWS.txt

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

Kai Wang commented on CASSANDRA-10904:
--------------------------------------

It would be helpful if the doc can include:
1. what are the "legacy tables" that should be dropped.
2. how to verify if the schema upgrade is successful. In my case, I get to know this change long after upgrade is done. There might be other errors in system.log but unrelated to the schema upgrade. Is there any "select this table, if abc and xyz are there, you are good" kind of way?

> 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
>
> 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)