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+

I've updated the DataStax blog post Reynald referred to earlier in the
thread and I'll commit an update to NEWS.txt with these instructions on
Monday.

Thanks,
Sam

On Sat, Dec 19, 2015 at 5:00 PM, Kai Wang <dep...@gmail.com> wrote:

> 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 Fri, Dec 18, 2015 at 9:23 AM, Kai Wang <dep...@gmail.com> wrote:
>
>> Sylvain,
>>
>> Thank you very much.
>>
>> On Fri, Dec 18, 2015 at 9:20 AM, Sylvain Lebresne <sylv...@datastax.com>
>> wrote:
>>
>>> On Fri, Dec 18, 2015 at 3:04 PM, Kai Wang <dep...@gmail.com> 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?
>>>>
>>>
>>> I didn't worked on those changes so I'm actually not sure of the exact
>>> answer. But I see you commented on the ticket so we'll make sure to include
>>> that information in the NEWS file (and maybe to get the blog post edited).
>>>
>>>
>>>>
>>>> Thanks.
>>>>
>>>>
>>>> On Fri, Dec 18, 2015 at 5:05 AM, Reynald Bourtembourg <
>>>> reynald.bourtembo...@esrf.fr> wrote:
>>>>
>>>>> 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 <
>>>>> <reynald.bourtembo...@esrf.fr>reynald.bourtembo...@esrf.fr> wrote:
>>>>>
>>>>>> This does not seem to be explained in the Cassandra 2.2 Upgrading
>>>>>> section of the NEWS.txt file:
>>>>>>
>>>>>>
>>>>>> https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/cassandra-2.2.4
>>>>>>
>>>>>>
>>>>> This is indeed an oversight. Would you mind opening a JIRA ticket so
>>>>> we don't forget to add it now?
>>>>>
>>>>> --
>>>>> Sylvain
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to