[
https://issues.apache.org/jira/browse/CASSANDRA-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038194#comment-13038194
]
Jonathan Ellis commented on CASSANDRA-2683:
-------------------------------------------
the serializer approach to skipping CL seems excessively complicated. why not
just have RMVH and RM.apply pass cfs.metadata.bypass_commitlog as the boolean
writeCommitlog parameter?
(note that RMVH is basically inlining RM.apply in its own Table.apply call, if
you fix that then there will be only one code path so even less risk of
confusion.)
> 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: v1-0001-CASSANDRA-2683-add-bypass_commitlog-flag.txt,
> v1-0002-CASSANDRA-2683-thrift-add-bypass_commitlog-flag.txt,
> v1-0003-CASSANDRA-2683-Fix-broken-unit-tests.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
