From 082af0a9ba6b5dde26055fcb9ddd2085e4240381 Mon Sep 17 00:00:00 2001 From: Joaquin Casares Date: Tue, 20 Jun 2017 18:26:26 -0500 Subject: [PATCH] Remove unused max_value_size_in_mb config setting Fixes #124 Patch by Joaquin Casares; Reviewed by Jeff Jirsa for CASSANDRA-13625 --- CHANGES.txt | 4 ++++ conf/cassandra.yaml | 5 ----- 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/CHANGES.txt b/CHANGES.txt index 56890c96e7..c966c92434 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,3 +1,7 @@ +2.2.11 + * Remove unused max_value_size_in_mb config setting from yaml (CASSANDRA-13625 + + 2.2.10 * Nodes started with join_ring=False should be able to serve requests when authentication is enabled (CASSANDRA-11381) * cqlsh COPY FROM: increment error count only for failures, not for attempts (CASSANDRA-13209) diff --git a/conf/cassandra.yaml b/conf/cassandra.yaml index 41c1fb19d9..c1c268c30f 100644 --- a/conf/cassandra.yaml +++ b/conf/cassandra.yaml @@ -885,11 +885,6 @@ enable_user_defined_functions: false # setting. windows_timer_interval: 1 -# Maximum size of any value in SSTables. Safety measure to detect SSTable corruption -# early. Any value size larger than this threshold will result into marking an SSTable -# as corrupted. -# max_value_size_in_mb: 256 - # Coalescing Strategies # # Coalescing multiples messages turns out to significantly boost message processing throughput (think doubling or more). # On bare metal, the floor for packet processing throughput is high enough that many applications won't notice, but in