[
https://issues.apache.org/jira/browse/CASSANDRA-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-1253.
---------------------------------------
Resolution: Later
> Forcing CL on a per user basis
> ------------------------------
>
> Key: CASSANDRA-1253
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1253
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Edward Capriolo
> Priority: Trivial
>
> The user that writes data is allowed to chose the CL they want. This presents
> several challenges for administration. For example, if I am sure ALL of our
> applications are writing/reading and CL.QUORUM or CL.ALL, I have some
> flexibility such as joining a node without auto-bootstrap. Also a policy
> might be made "all data must be written at QUORUM".
> The new feature is to associate users with a list of available CL. Thus an
> administrator can enable disable levels.
> {noformat}
> admin: read level [ CL.ZERO,CL.ONE,CL.QUORUM, CL.ALL ]
> user1: read level [CL.QUORUM, CL.ALL]
> {noformat}
> If the user attempts to write/read with a disallowed level an Exception can
> be thrown or the request could be silently modified/upgraded to a different
> CL.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
