cassandra-commits mailing list archives

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

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

Jeremiah Jordan commented on CASSANDRA-7296:
--------------------------------------------

Besides what the client API looks like how would people expect this to behave if the coordinator
is not a replica?  That decision may also affect how the API should look from a "least surprises"
stand point. If the CL was "THIS_ONE" I would expect no data or possibly an UnavailableException
(IIRC this is what you get from LOCAL_ in a DC with no replicas). If it was a flag called
"prefer coordinator" of something then I would expect the request to be coordinated to replica
nodes if the coordinator wasn't one.

> 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