cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7296) Add CL.COORDINATOR_ONLY
Date Mon, 10 Oct 2016 17:28:21 GMT

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

Blake Eggleston commented on CASSANDRA-7296:
--------------------------------------------

Just to clarify, has the goal of the ticket changed to give operators the option to always
include the coordinator in a read if it's a replica? The goal as stated in the ticket description
is to give operators the option to perform a local only read against the coordinator they’ve
connected to, and fail (or return nothing) if it's not a replica.

In the context of the original description, combining this option with CLs other than ONE
doesn’t make much sense.

> Add CL.COORDINATOR_ONLY
> -----------------------
>
>                 Key: CASSANDRA-7296
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7296
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Tupshin Harper
>
> For reasons such as CASSANDRA-6340 and similar, it would be nice to have a read that
never gets distributed, and only works if the coordinator you are talking to is an owner of
the row.



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

Mime
View raw message