cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13371) Remove legacy auth tables support
Date Mon, 31 Jul 2017 12:44:00 GMT

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

Stefan Podkowinski commented on CASSANDRA-13371:
------------------------------------------------

How about using the startup check for that and make it log to warn in 3.0/3.11 and start throwing
a StartupException in 4.0?



> Remove legacy auth tables support
> ---------------------------------
>
>                 Key: CASSANDRA-13371
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13371
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Auth
>            Reporter: Stefan Podkowinski
>            Assignee: Stefan Podkowinski
>              Labels: security
>             Fix For: 4.x
>
>
> Starting with Cassandra 3.0, we include support for converting pre CASSANDRA-7653 user
tables, until they will be dropped by the operator. Converting e.g. permissions happens by
simply copying all of them from {{permissions}} -> {{role_permissions}}, until the {{permissions}}
table has been dropped.
> Upgrading to 4.0 will only be possible from 3.0 upwards, so I think it's safe to assume
that the new permissions table has already been populated, whether the old table was dropped
or not. Therefor I'd suggest to just get rid of the legacy support.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message