cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-300) Enumerate useful consistency options for read/write calls
Date Tue, 28 Jul 2009 13:31:15 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736062#action_12736062
] 

Hudson commented on CASSANDRA-300:
----------------------------------

Integrated in Cassandra #151 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/151/])
    add ConsistencyLevel Thrift enum to avoid client having to compute quorum size. patch
by Sammy Yu; reviewed by jbellis for 


> Enumerate useful consistency options for read/write calls
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-300
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-300
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Michael Greene
>            Assignee: Sammy Yu
>             Fix For: 0.4
>
>         Attachments: 0001-Work-for-CASSANDRA-300.patch, 0002-Patch-for-CASSANDRA-300.patch
>
>
> Currently, a user has to specify an int for the number of nodes to block_for.  As discussed
on IRC, there are only a few options that a user would want, so this would be better encapsulated
by an enum.
> enum  ConsistencyLevel {
>     ZERO = 0,
>     ONE = 1,
>     QUORUM = 2,
>     ALL = 3,
> }
> This could be extended with a fifth option, CUSTOM = 4, if custom specifications are
desired
> struct ConsistencyRequest {
>     1: required ConsistencyLevel level,
>     2: optional int nodes
> }

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