gora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Renato Javier Marroquín Mogrovejo (JIRA) <j...@apache.org>
Subject [jira] [Commented] (GORA-167) Make Cassandra keyspace consistency configurable within gora.properties
Date Wed, 05 Mar 2014 16:46:44 GMT

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

Renato Javier Marroquín Mogrovejo commented on GORA-167:
--------------------------------------------------------

Hi [~lewismc],

This is a cool patch mate. This works as expected :)
I think what we could do is to extend this property to also allow consistency levels per operation
as Cassandra also allows. So maybe we should change the property name as the patch is currently
using as a default "ColumnFamily" consistency level.
So I think maybe using a different property name, something like: gora.cassandrastore.cf.consistency.level
and gora.cassandrastore.read.consistency.level for when that gets in. Wdyt?
And also IMHO the 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.


> 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
(v6.2#6252)

Mime
View raw message