You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2015/02/21 03:03:12 UTC

[jira] [Commented] (CASSANDRA-7296) Add CL.COORDINATOR_ONLY

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

Jeff Jirsa commented on CASSANDRA-7296:
---------------------------------------

Untested patch available at https://github.com/jeffjirsa/cassandra/compare/cassandra-7296.diff 
CQLSH requires python driver updated/patch at https://github.com/jeffjirsa/python-driver/compare/coordinator-only.diff 

I have no idea if there's interest in actually merging this (that is, if the project actually wants CL.COORDINATOR_ONLY). I can see use cases where people might want it. I'm not sure if it's worth the added complexity on the project. If someone confirms there's interest, I'll do more thorough testing. 

> 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)