cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Haddad (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7296) Add CL.COORDINATOR_ONLY
Date Wed, 17 Dec 2014 18:04:14 GMT

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

Jon Haddad commented on CASSANDRA-7296:
---------------------------------------

Good points.  I think this issue would result in other, perhaps more serious problems, making
an appearance.  I am not convinced, however, that NUM_TOKENS = NUM_QUERIES is the right solution
on the spark side either, under the case of (data > disk && disk_type == spinning_rust).
 I think we can move any future discussion to the driver JIRA and reference this from there.

> 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