You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/05/25 03:30:47 UTC

[jira] [Commented] (CASSANDRA-2683) Allow writes to bypass the commit log for certain keyspaces

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

Jonathan Ellis commented on CASSANDRA-2683:
-------------------------------------------

Looks good.

Final nit: "don't do something" boolean options are not as easily understood as "do something" -- would rather call this "durable_writes" or similar.

> Allow writes to bypass the commit log for certain keyspaces
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-2683
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2683
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>             Fix For: 0.8.1
>
>         Attachments: v1-0001-CASSANDRA-2683-add-bypass_commitlog-flag.txt, v1-0002-CASSANDRA-2683-thrift-add-bypass_commitlog-flag.txt
>
>
> Some data in cassandra does not need durability on a single node.  Also ec2 users often wish to disable the commitlog since they are using the ephemeral disks.
> This patch let's you set bypass_commitlog=true in the CfMetaData, the effect being RowMutations on ColumnFamilies with this flag will bypass the commit log

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira