[ https://issues.apache.org/jira/browse/CASSANDRA-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418765#comment-13418765 ]
Jonathan Ellis commented on CASSANDRA-4448: ------------------------------------------- I'll be more specific: nobody *should* write raw JDBC at the app layer. This is not something I want to encourage. (And holding up Hector as a straw man is a cheap shot; you won't find a single instance of me praising Hector's API.) As I've already said: I recognize that the hypothetical good Java API built on CQL doesn't exist yet, but let's be a little forward-looking and imagine what we should build if it did. (Because it will, soon enough.) > 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 > 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 (...) > WITH DEFAULT_READ_CONSISTENCY = QUORUM > AND DEFAULT_WRITE_CONSISTENCY = QUORUM > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira