[
https://issues.apache.org/jira/browse/CASSANDRA-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733828#action_12733828
]
Jonathan Ellis commented on CASSANDRA-300:
------------------------------------------
It does mean that the client doesn't have to know what QUORUM means (and we
have a ticket to make that configurable per table/keyspace).
> Doesn't it make more sense to switch to an enum where there's a better
> understanding of what custom levels entail?
Not sure, what did you have in mind?
> 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
>
> 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.
