You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by jb...@apache.org on 2009/09/29 20:41:11 UTC
svn commit: r820064 - /incubator/cassandra/trunk/conf/storage-conf.xml
Author: jbellis
Date: Tue Sep 29 18:41:11 2009
New Revision: 820064
URL: http://svn.apache.org/viewvc?rev=820064&view=rev
Log:
make FlushPeriodInMinutes comment more accurate. patch by jbellis
Modified:
incubator/cassandra/trunk/conf/storage-conf.xml
Modified: incubator/cassandra/trunk/conf/storage-conf.xml
URL: http://svn.apache.org/viewvc/incubator/cassandra/trunk/conf/storage-conf.xml?rev=820064&r1=820063&r2=820064&view=diff
==============================================================================
--- incubator/cassandra/trunk/conf/storage-conf.xml (original)
+++ incubator/cassandra/trunk/conf/storage-conf.xml Tue Sep 29 18:41:11 2009
@@ -59,9 +59,9 @@
~ (To get the closest approximation to 0.3-style supercolumns, you
~ would use CompareWith=UTF8Type CompareSubcolumnsWith=LongType.)
- ~ If FlushPeriodInMinutes is configured and positive, it will be
- ~ flushed to disk with that period whether it is dirty or not. This
- ~ is intended for lightly-used columnfamilies so that they do not
+ ~ If FlushPeriodInMinutes is positive, it will be
+ ~ flushed to disk with that period even if the memtable has not
+ ~ exceeded the size or count thresholds, so that it does not
~ prevent commitlog segments from being purged.
-->
<ColumnFamily CompareWith="BytesType"