[
https://issues.apache.org/jira/browse/CASSANDRA-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273600#comment-14273600
]
Sylvain Lebresne commented on CASSANDRA-7653:
---------------------------------------------
bq. I think it's probably acceptable for us to change metadata like this in a
major release, particularly as the semantics and structure of the resultset is
unchanged
The problem is that it makes it really hard during rolling upgrade, because a
given client will talk to server in both version and so you'd need code just
for the migration to test if a column or the other is present. So I agree that
we need to have both column for at least one version. It's not perfect, some
will wonder if there is a difference between the two, but it's better than the
alternative.
> Add role based access control to Cassandra
> ------------------------------------------
>
> Key: CASSANDRA-7653
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7653
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Mike Adamson
> Assignee: Sam Tunnicliffe
> Fix For: 3.0
>
> Attachments: 7653.patch, CQLSmokeTest.java, cql_smoke_test.py
>
>
> The current authentication model supports granting permissions to individual
> users. While this is OK for small or medium organizations wanting to
> implement authorization, it does not work well in large organizations because
> of the overhead of having to maintain the permissions for each user.
> Introducing roles into the authentication model would allow sets of
> permissions to be controlled in one place as a role and then the role granted
> to users. Roles should also be able to be granted to other roles to allow
> hierarchical sets of permissions to be built up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
