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 Mon, 10 Oct 2016 17:39:20 GMT

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

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

I'm very opposed to the /\*disable_snitch=true\*/ syntax.  We don't use that anywhere, and
why would we want that to be part of the statement?  Making it part of the statement removes
the ability to disable dynamic snitch at a _per query_ level, including it as part of CQL
makes it per prepared statement.  

It's not like adding it to the protocol is any different than specifying consistency level
or a write timestamp.  

> 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