Remove binary_memtable_throughput_in_mb from yaml to avoid confusion

git-svn-id: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@1080806 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Brandon Williams 2011-03-11 23:55:08 +00:00
parent 0699bea298
commit 1c12d7bd9c
1 changed files with 0 additions and 4 deletions

View File

@ -228,10 +228,6 @@ snapshot_before_compaction: false
# lowest priority and that is our default.
# compaction_thread_priority: 1
# The threshold size in megabytes the binary memtable must grow to,
# before it's submitted for flushing to disk.
binary_memtable_throughput_in_mb: 256
# Add column indexes to a row after its contents reach this size.
# Increase if your column values are large, or if you have a very large
# number of columns. The competing causes are, Cassandra has to