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

Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2011/05/21 22:33:47 UTC

[jira] [Updated] (CASSANDRA-2683) Allow writes to bypass the commit log for certain column families

     [ https://issues.apache.org/jira/browse/CASSANDRA-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

T Jake Luciani updated CASSANDRA-2683:
--------------------------------------

    Attachment: 2683_v1.txt

> Allow writes to bypass the commit log for certain column families
> -----------------------------------------------------------------
>
>                 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: 2683_v1.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