cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7296) Add CL.COORDINATOR_ONLY
Date Fri, 07 Oct 2016 19:03:20 GMT


Edward Capriolo commented on CASSANDRA-7296:

 Since there's little upside to this, and quite a bit of potential downside

This is really useful if you want to do user generated request pinning. ONE could allows the
node to proxy the request away based on what dynamic_snitch wants to do.

New consistency levels tend to introduce a lot of edge-case bugs, and this one is particularly
special, which probably means extra bugs.

I am not following this logic. Why does because previously attempts which added buggy or incomplete
features stand as a reason not to add new features?

> -----------------------
>                 Key: CASSANDRA-7296
>                 URL:
>             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

View raw message