gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GORA-167) Make Cassandra keyspace consistency configurable within gora.properties
Date Wed, 05 Mar 2014 16:54:43 GMT

    [ https://issues.apache.org/jira/browse/GORA-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921037#comment-13921037

Lewis John McGibbney commented on GORA-167:

bq. ...also allow consistency levels per operation as Cassandra also allows.
+1 definately

So you're proposing the following as properties to be added to gora.properties

gora.cassandrastore.cf.consistency.level (presumably this one accommodates writes into Cassandra?)

bq. default consistency level should be the one provided by the client so users don't get
more confused. Hector uses Quorum consistency level as a default.

No probs at all. I agree here as well. This is my fault and it should be client preference
by default.

If you're keen to implement these changes please fire away, if not then say so and I will
try to implement them.

> Make Cassandra keyspace consistency configurable within gora.properties
> -----------------------------------------------------------------------
>                 Key: GORA-167
>                 URL: https://issues.apache.org/jira/browse/GORA-167
>             Project: Apache Gora
>          Issue Type: Improvement
>          Components: gora-cassandra
>    Affects Versions: 0.2.1
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Minor
>             Fix For: 0.4
>         Attachments: GORA-167.patch, GORA-167v2.patch, GORA-167v3.patch
> Current in CassandraClient#checkKeyspace() consistency is hard coded such that consistency
level is .ONE which permits consistency to wait until one replica has responded. This could
be improved to enable users to specify other consistency profiles e.g. 
>         ANY: Wait until some replica has responded.
>         ONE: Wait until one replica has responded.
>         TWO: Wait until two replicas have responded.
>         THREE: Wait until three replicas have responded.
>         LOCAL_QUORUM: Wait for quorum on the datacenter the connection was stablished.
>         EACH_QUORUM: Wait for quorum on each datacenter.
>         QUORUM: Wait for a quorum of replicas (no matter which datacenter).
>         ALL: Blocks for all the replicas before returning to the client.
> Configuration should be made available through gora.properties

This message was sent by Atlassian JIRA

View raw message