cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-6970) Support CL=EACH_QUORUM for reads
Date Mon, 05 Oct 2015 07:55:27 GMT

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

Sylvain Lebresne resolved CASSANDRA-6970.
-----------------------------------------
    Resolution: Duplicate

> Support CL=EACH_QUORUM for reads
> --------------------------------
>
>                 Key: CASSANDRA-6970
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6970
>             Project: Cassandra
>          Issue Type: Wish
>         Environment: SLES 11 SP3 x86_64
> Cassandra 2.0.6
>            Reporter: Oliver Seiler
>
> SELECTs done at CL=EACH_QUORUM get an InvalidRequestException: with a message of "EACH_QUORUM
ConsistencyLevel is only supported for writes".
> The documentation doesn't indicate this would happen, so at minimum this is inconsistent
with the current documentation. I'm aware of CASSANDRA-3272, which indicates this has never
worked as expected, and made this obvious with the InvalidRequestException.
> I'm not sure why this shouldn't work, regardless of Jonathan Ellis commenting "I ask
because I've never seen it to be the 'right' CL yet". I'd like it because: I want to do my
writes at LOCAL_QUORUM and (some) reads at EACH_QUORUM, because I require guaranteed consistency
for (some) reads where I can be partition intolerant without affecting clients, rather than
becoming partition intolerant on writes...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message