cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4448) CQL3: allow to define a per-cf default consistency level
Date Fri, 06 Dec 2013 05:02:35 GMT

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

Jonathan Ellis commented on CASSANDRA-4448:
-------------------------------------------

This was removed in CASSANDRA-4734, between 1.2.0b1 and 1.2.0b2.  So not only was this not
removed in 1.2.10 but it was never included in 1.2.0-final.

> 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)

Mime
View raw message