cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4448) CQL3: allow to define a per-cf default consistency level
Date Thu, 19 Jul 2012 17:00:38 GMT


Jonathan Ellis commented on CASSANDRA-4448:

bq. It is especially true for a client like JDBC which really is not designed to have any
DB specific controls

Modern Java apps use JDBC as a low-level driver.  Nobody writes raw JDBC code at the app layer.

bq. I think it is more convenient to set that once at the table creation rather that having
to call setReadConsistencyLevel() and setWriteConsistencyLevel() every time you create your
ColumnFamily object in the application code

But you create CF objects exactly once and then import them elsewhere.
> CQL3: allow to define a per-cf default consistency level
> --------------------------------------------------------
>                 Key: CASSANDRA-4448
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Sylvain Lebresne
>              Labels: cql3
>             Fix For: 1.2
> 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 (...)
> {noformat}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message