[
https://issues.apache.org/jira/browse/CASSANDRA-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565718#comment-15565718
]
Jeremy Hanna commented on CASSANDRA-7296:
-----------------------------------------
It does look like given the use case and that it really only applies to CL.ONE,
it does look like the CL addition is a clearer/cleaner option. It makes using
the rest of the driver options simpler to reason about because it makes the CL
contract very clear regardless of the other options. The driver changes appear
to have the same level of intrusiveness and the protocol would have to be
updated in either case.
Is there a reason why a CL addition couldn't be done in this case - or in other
words, do the edge cases of adding a CL outweigh the clarity of this function
as a CL?
> 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)
