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 15:42:34 GMT


Jonathan Ellis commented on CASSANDRA-4448:

If you're playing with cqlsh, on the rare occasions that you need to specify CL doing so manually
is not a big deal.  But if you're writing application code, you should not be writing raw
CQL; you should be using a higher-level, idiomatic API (such as the one pycassa provides),
which can generate CQL specifying CL with no work on your part.

Granted, such higher-level APIs do not yet exist for CQL, but I think this is a misfeature
given that we will get to that point in the next few months.
> 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