Sorry about the confusing omission of the upgrade instructions from
NEWS.txt, the oversight there was mine in the course of CASSANDRA-7653.
Dropping those tables is absolutely what you need to do in order to trigger
C* to switch over to using the new role-based tables following an upgrade
to 2.2+
Some update. I went through this blog:
https://www.instaclustr.com/5-things-you-need-to-know-about-cassandra-2-2/
and deleted these three tables (with fingers crossed):
system_auth.credentials
system_auth.users
system_auth.permissions
Now I seem to be able to use RBAC to modify permissions.
On
Sylvain,
Thank you very much.
On Fri, Dec 18, 2015 at 9:20 AM, Sylvain Lebresne
wrote:
> On Fri, Dec 18, 2015 at 3:04 PM, Kai Wang wrote:
>
>> Reynald,
>>
>> Thanks for link. That explains it.
>>
>> Sylvain,
>>
>> What exactly are the "legacy tables" I am supposed to drop? Before I drop
>> the
On Fri, Dec 18, 2015 at 3:04 PM, Kai Wang wrote:
> Reynald,
>
> Thanks for link. That explains it.
>
> Sylvain,
>
> What exactly are the "legacy tables" I am supposed to drop? Before I drop
> them, is there any way I can confirm the old schema has been converted to
> the new one successfully?
>
Reynald,
Thanks for link. That explains it.
Sylvain,
What exactly are the "legacy tables" I am supposed to drop? Before I drop
them, is there any way I can confirm the old schema has been converted to
the new one successfully?
Thanks.
On Fri, Dec 18, 2015 at 5:05 AM, Reynald Bourtembourg <
re
Done:
https://issues.apache.org/jira/browse/CASSANDRA-10904
On 18/12/2015 10:51, Sylvain Lebresne wrote:
On Fri, Dec 18, 2015 at 8:55 AM, Reynald Bourtembourg
mailto:reynald.bourtembo...@esrf.fr>>
wrote:
This does not seem to be explained in the Cassandra 2.2 Upgrading
section of the
