[
https://issues.apache.org/jira/browse/CASSANDRA-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121455#comment-13121455
]
Frank Yang commented on CASSANDRA-3319:
---------------------------------------
so, let me understand it correctly.
I can implement my own hook, and configure the yaml to use it. no problem.
but, during each production upgrade to the next version of cassie, i need to
remember to carry my hook with it?
that is certainly doable, but not desirable. If our implementations are added
to the standard releases, then, we wouldn't have to worry about, right? the
conditions for inclusion should only be that 1. it builds and 2. the naming
makes sense. and 3. some documentation is included so that others can also
benefit from it. IMO.
> IAuthority implementation to allow all keyspace access based on r/w on
> keyspace only
> ------------------------------------------------------------------------------------
>
> Key: CASSANDRA-3319
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3319
> Project: Cassandra
> Issue Type: New Feature
> Components: Contrib
> Affects Versions: 0.8.7
> Reporter: Frank Yang
> Labels: patch
> Attachments: SimpleKeyspaceBasedAuthority.java
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> SimpleAuthority checks CF access based on specific instructions for that CF
> in the access.properties file.
> This is not usable. eg, every time a developer adds a CF, the admin needs to
> modify the access.properties file, on all the nodes.
> A different, friendlier implementation should grant CF access based on
> keyspace permissions.
> Keyspace1.<rw> ==> modify keyspace1 AND any CF inside of it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
