[
https://issues.apache.org/jira/browse/CASSANDRA-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841010#comment-13841010
]
Jonathan Ellis commented on CASSANDRA-4448:
-------------------------------------------
Ah, I see -- the actual columns weren't removed until cb0a0cd this August. But
they've been doing absolutely nothing in the meantime.
> CQL3: allow to define a per-cf default consistency level
> --------------------------------------------------------
>
> Key: CASSANDRA-4448
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4448
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Labels: cql3
> Fix For: 1.2.0 beta 1
>
> Attachments: 4448.txt
>
>
> One of the goal of CQL3 is that client library should not have to parse
> queries to provide a good experience. In particular, that means such client
> (that don't want to parse queries) won't be able to allow the user to define
> a specific default read/write consistency level per-CF, forcing user to
> specific the consistency level with every query, which is not very user
> friendly.
> This ticket suggests the addition of per-cf default read/write consitency
> level. Typically the syntax would be:
> {noformat}
> CREATE TABLE foo (...)
> WITH DEFAULT_READ_CONSISTENCY = QUORUM
> AND DEFAULT_WRITE_CONSISTENCY = QUORUM
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
