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

Tiago L. Alves commented on CASSANDRA-20863:
--------------------------------------------

{quote} I am OK to add them back to 5.0 but I am not sure we should continue to 
have two ways in trunk, there should be just one approach, the newest one.

The patch is for trunk. I think it should be for 5.0 and we should keep trunk 
untouched.
{quote}
 

I totally agree that this patch should go for 5.0.

I forgot about asking about the deprecation policy for C* versions. Given trunk 
is the upcoming 6.0 version this warning should no longer be needed. Is that 
right?

 
{quote}Well, looking into this I think that will be more involved. Let's just 
ship what we have in the patch as is just to bring them back and we can 
contemplate about any improvements later
{quote}
What do you mean?

 

> Missing authorizer and role_manager configs in system_views.settings
> --------------------------------------------------------------------
>
>                 Key: CASSANDRA-20863
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20863
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Feature/Virtual Tables
>            Reporter: Sudipta Laha
>            Assignee: Shruti Sekaran
>            Priority: Normal
>             Fix For: 5.0.x, 5.x
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Authorizer role_manager configs are missing in system_views.settings after 
> the changes in CASSANDRA-19946 were merged. Example query on a 5.x cluster:
>  
> cqlsh> select * from system_views.settings where name = 'authorizer';
>  name | value
> ------+-------
> cqlsh> select * from system_views.settings where name = 'role_manager';
>  name | value
> ------+-------
> (0 rows)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to