svn commit: r952046 - in /websites/staging/accumulo/trunk/content: ./ release_notes/1.7.0.html

[bu...@apache.org]

Author: buildbot
Date: Wed May 20 14:57:06 2015
New Revision: 952046

Log:
Staging update by buildbot for accumulo

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

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed May 20 14:57:06 2015
@@ -1 +1 @@
-1680587
+1680588

Modified: websites/staging/accumulo/trunk/content/release_notes/1.7.0.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/1.7.0.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/1.7.0.html Wed May 20 14:57:06 2015
@@ -455,7 +455,7 @@ introduces a new per-table property whic
 <code>VolumeChooser</code>. This ensures that the implementation to choose how HDFS
 utilization happens when multiple are available is limited to the expected
 subset of all tables.</p>
-<h3 id="table-and-namespace-custom-properties">Table and namespace custom properties</h3>
+<h2 id="table-and-namespace-custom-properties">Table and namespace custom properties</h2>
 <p>Inorder to avoid errors caused by mis-typed configuration properties, Accumulo was strict about which configuration properties 
 could be set.  However this prevented user from setting arbitrary properties that could be used by custom balancers, compaction 
 strategies, volume choosers, and iterators.  Under <a href="https://issues.apache.org/jira/browse/ACCUMULO-2841">ACCUMULO-2841</a> the ability to set arbitrary table and