Author: buildbot
Date: Mon May  5 16:54:09 2014
New Revision: 908119

Log:
Staging update by buildbot for accumulo

Modified:
    websites/staging/accumulo/trunk/content/   (props changed)
    websites/staging/accumulo/trunk/content/release_notes/1.6.0.html

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon May  5 16:54:09 2014
@@ -1 +1 @@
-1592559
+1592569

Modified: websites/staging/accumulo/trunk/content/release_notes/1.6.0.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/1.6.0.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.6.0.html Mon May  5 
16:54:09 2014
@@ -282,8 +282,8 @@ issues such as JVM garbage collection pa
 
 
 <p>Be aware that you will need a C++ compiler/toolchain installed to build 
this library. Check your GNU/Linux distribution documentation for the package 
manager command.</p>
-<h4 id="size-based-constraint-on-new-tables">Size-Based Constraint on New 
Tables</h4>
-<p>A Constraint is an interface that can determine if a Mutation should be 
applied or rejected server-side. New tables that are created in 1.6.0 will 
automatically have the <code>DefaultKeySizeConstraint</code> set.
+<h3 id="size-based-constraint-on-new-tables">Size-Based Constraint on New 
Tables</h3>
+<p>A Constraint is an interface that can determine if a Mutation should be 
applied or rejected server-side. After <a 
href="https://issues.apache.org/jira/browse/ACCUMULO-466";>ACCUMULO-466</a>, new 
tables that are created in 1.6.0 will automatically have the 
<code>DefaultKeySizeConstraint</code> set.
 As performance can suffer when large Keys are inserted into a table, this 
Constraint will reject any Key that is larger than 1MB. If this constraint is 
undesired, it can be removed using the <code>constraint</code> shell
 command. See the help message on the command for more information.</p>
 <h3 id="other-notable-changes">Other notable changes</h3>


Reply via email to