From 44b6e99e1b49193198b021c87d7f173ba1858184 Mon Sep 17 00:00:00 2001 From: agiardullo Date: Tue, 8 Sep 2015 17:54:35 -0700 Subject: [PATCH] update max_write_buffer_number_to_maintain docblock Summary: fix comment Test Plan: n/a Reviewers: sdong, IslamAbdelRahman Reviewed By: IslamAbdelRahman Subscribers: dhruba, leveldb Differential Revision: https://reviews.facebook.net/D46455 --- include/rocksdb/options.h | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/include/rocksdb/options.h b/include/rocksdb/options.h index 4c457f8ed0..ee47f5d71f 100644 --- a/include/rocksdb/options.h +++ b/include/rocksdb/options.h @@ -276,10 +276,9 @@ struct ColumnFamilyOptions { // If this value is set to -1, 'max_write_buffer_number' will be used. // // Default: - // If using an OptimisticTransactionDB, the default value will be set to the - // value - // of 'max_write_buffer_number' if it is not explicitly set by the user. - // Otherwise, the default is 0. + // If using a TransactionDB/OptimisticTransactionDB, the default value will + // be set to the value of 'max_write_buffer_number' if it is not explicitly + // set by the user. Otherwise, the default is 0. int max_write_buffer_number_to_maintain; // Compress blocks using the specified compression algorithm. This