cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-2683) Allow writes to bypass the commit log for certain column families
Date Sat, 21 May 2011 20:35:47 GMT

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

T Jake Luciani commented on CASSANDRA-2683:
-------------------------------------------

Seems like thrift generated code changed a bunch, I'm using the thrift-0.6 compiler.  

> 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

Mime
View raw message