Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 6 Feb 2015 18:56:36 +0000 (UTC)
From: "Wei Deng (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12773061.1423244223000.282053.1423248996212@Atlassian.JIRA>
In-Reply-To: <JIRA.12773061.1423244223000@Atlassian.JIRA>
References: <JIRA.12773061.1423244223000@Atlassian.JIRA>
 <JIRA.12773061.1423244223901@arcas>
Subject: [jira] [Commented] (CASSANDRA-8754) Required consistency level
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Wei Deng commented on CASSANDRA-8754:
-------------------------------------

+1 to Ryan. Especially when we are talking about reviewing code in all languages the Cassandra drivers support.

> Required consistency level
> --------------------------
>
>                 Key: CASSANDRA-8754
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8754
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Ryan Svihla
>              Labels: ponies
>
> Idea is to prevent a query based on a consistency level not being met. For example we can specify that all queries should be at least CL LOCAL_QUORUM.
> Lots of users struggle with getting all their dev teams on board with consistency levels and all the ramifications. The normal solution for this has traditionally to build a service in front of Cassandra that the entire dev team accesses. However, this has proven challenging for some organizations to do correctly, and I think an easier approach would be to require a given consistency level as a matter of enforced policy in the database. 
> I'm open for where this belongs. The most flexible approach is at a table level, however I'm concerned this is potentially error prone and labor intensive. It could be a table attribute similar to compaction strategy.
> The simplest administratively is a cluster level, in say the cassandra.yaml
> The middle ground is at they keyspace level, the only downside I could foresee is keyspace explosion to fit involved minimum schemes. It could be a keyspace attribute such as replication strategy.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)