[
https://issues.apache.org/jira/browse/CASSANDRA-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562659#comment-15562659
]
Sylvain Lebresne commented on CASSANDRA-7296:
---------------------------------------------
bq. I'm concerned it will prove to be a step backwards in real clusters, where
coordinator disk latencies may truly jump up up significantly
Right, by we also have rapid read protection now that might limit that problem
reasonably well. But anyway, I'm not making any strong claim here, that's why I
started my sentence by "I'm not even entirely sure". Basically, despite this
being arguably confusing to most, I'm not sure we have really quantified the
advantage this brings us, which is a shame (but it's not like I'm volunteering
for experimenting here so ....).
To clarify, my main point was that I dislike the idea of providing this through
a new CL, and I'd rather have that being a protocol level query option (we have
to change the protocol _anyway_).
> 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)
