[
https://issues.apache.org/jira/browse/CASSANDRA-2683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038203#comment-13038203
]
Jonathan Ellis commented on CASSANDRA-2683:
-------------------------------------------
I think there's a further wrinkle here: Table.apply and RM are per-keyspace,
but CL-skipping is per-CF. (Is that why you took the serializer approach? If
so, I'm a bit slow.)
I'm still not a fan of making it more complex, though. I'd rather just && the
bypass values together and if any CF wants the CL, we throw the whole RM into
it. IMO mixing bypassed- and non- in the same batch is not something we should
encourage anyway.
> 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
