cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <>
Subject [jira] Reopened: (CASSANDRA-1253) Forcing CL on a per user basis
Date Thu, 22 Jul 2010 14:30:51 GMT


Edward Capriolo reopened CASSANDRA-1253:

Sure this is a client side issue, but it is too easy for clients to just use the default 0
say from some pieces of middle ware, and never be aware of the setting. As an administrator
I often have to force users to do the right thing. One example is passwords that expire, everyone
knows set a hard password and change it periodically, but can we count on the user to do that?
The same is true here. I feel that some developers may not understand the constancy model
as well as they should and nothing stops them from writing ANY,or ONE. As an administrator
I can not do code audits to ensure that everyone is using the level they are supposed to,
it worries me that clients may automatically be choosing 0.

> Forcing CL on a per user basis
> ------------------------------
>                 Key: CASSANDRA-1253
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Edward Capriolo
> 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.

View raw message