[
https://issues.apache.org/jira/browse/CASSANDRA-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563043#comment-15563043
]
Edward Capriolo edited comment on CASSANDRA-7296 at 10/10/16 6:20 PM:
----------------------------------------------------------------------
{quote}
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.
{quote}
Again, this is how most (if not all databases do this). The reason is for RDBMS
databases the API's are standard (like JDBC) and you can not add new
functionality in the form of new methods.
The win of CQL is it solves everything in the query language. Everything else
takes something out of the language makes it more like thirft. It is now
something that EVERY client driver must implement.
This is why the consistency level makes sense as well because you can fit the
need without making a new feature that all the clients must implement to get
the functionality
was (Author: appodictic):
{quote}
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.
{quote}
Again, this is how most (if not all databases do this). The reason is for RDBMS
databases the API's are standard (like JDBC) and you can not add new
functionality in the form of new methods.
The point of CQL is it solves everything in the query language, every weird
switch that takes something out of the language makes it more like thirft. It
is now something that EVERY client drive must implement.
> 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)
