Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 24 Feb 2015 01:13:13 +0000 (UTC)
From: "Tyler Hobbs (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12716516.1400958555000.117210.1424740393742@Atlassian.JIRA>
In-Reply-To: <JIRA.12716516.1400958555000@Atlassian.JIRA>
References: <JIRA.12716516.1400958555000@Atlassian.JIRA>
 <JIRA.12716516.1400958555260@arcas>
Subject: [jira] [Commented] (CASSANDRA-7296) Add CL.COORDINATOR_ONLY
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tyler Hobbs commented on CASSANDRA-7296:
----------------------------------------

It seems like the primary motivation here was performance and the use-case mentioned in CASSANDRA-6340.  The performance concern seems to have been address thoroughly by Piotr, and as I commented on 6340, I'm not sure this is the best solution there either.

New consistency levels tend to introduce a lot of edge-case bugs, and this one is particularly special, which probably means extra bugs.  Since there's little upside to this, and quite a bit of potential downside, I vote for closing this as Won't Fix.

> Add CL.COORDINATOR_ONLY
> -----------------------
>
>                 Key: CASSANDRA-7296
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7296
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Tupshin Harper
>            Assignee: Jeff Jirsa
>
> 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)