[
https://issues.apache.org/jira/browse/CASSANDRA-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556007#comment-15556007
]
Tupshin Harper commented on CASSANDRA-7296:
-------------------------------------------
Given the fresh activity, I'd like to re-emphasize my support for this ticket.
I think node/data debugging via request pinning is an excellent use of it, and
is basically the original reason for the ticket. Spark turned out to be an
irrelevant tangent, but there is significant benefit in supporting this
(degeneratively simple) form of consistency. If [~jjirsa]'s patch is still
applicable (or can be), i'd love to see it given a fair shake.
> 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)
