cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-1253) Forcing CL on a per user basis
Date Tue, 06 Jul 2010 16:21:50 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Edward Capriolo updated CASSANDRA-1253:
---------------------------------------

    Description: 
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.

  was:
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}


> 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
>
> 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.


Mime
View raw message