[CASSANDRA-8754] Required consistency level

• Type: New Feature
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Component/s: Feature/Lightweight Transactions
• Labels: LWT ponies
• Assignee: Unassigned
• Reporter: Ryan Svihla
• Created: 06/Feb/15 17:37
• Updated: 25/Oct/19 13:11
• Resolved: 05/Mar/15 03:18

Description

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.

Issue Links

• duplicates: CASSANDRA-8303 Create a capability limitation framework