svn commit: r866638 - in /websites/staging/accumulo/trunk/content: ./ notable_features.html

[bu...@apache.org]

Author: buildbot
Date: Thu Jun 20 14:43:06 2013
New Revision: 866638

Log:
Staging update by buildbot for accumulo

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

Propchange: websites/staging/accumulo/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jun 20 14:43:06 2013
@@ -1 +1 @@
-1494984
+1495029

Modified: websites/staging/accumulo/trunk/content/notable_features.html
==============================================================================
--- websites/staging/accumulo/trunk/content/notable_features.html (original)
+++ websites/staging/accumulo/trunk/content/notable_features.html Thu Jun 20 14:43:06 2013
@@ -129,11 +129,11 @@ which master is active.  The remaining m
 master to lose its lock.  Current master state is held in the metadata table
 and Zookeeper (see <a href="#fate">FATE</a>).</p>
 <h3 id="write-ahead-log">Write ahead log</h3>
-<p>Tablet servers send mutations to loggers, not HDFS.  Each mutation is written
-to multiple loggers, before being committed.  In normal configurations, loggers
+<p>In version 1.4, tablet servers send mutations to loggers which write to the local file system, not HDFS.<br />
+Each mutation is written to multiple loggers, before being committed.  In normal configurations, loggers
 are run on every server that runs a tablet server.  When a log is needed for
 recovery, it is copied into HDFS.  For efficient recovery, the log is sorted as
-it is copied.</p>
+it is copied.  In version 1.5, write ahead logs are written to HDFS, and loggers are no longer needed.</p>
 <h3 id="logical-time">Logical time</h3>
 <p>A mechanism to ensure that server set times never go backwards, even when time
 across the cluster is incorrect. This ensures that updates and deletes are not
@@ -356,7 +356,8 @@ This is useful for increasing ingest per
 used to accommodate new data patterns in an existing table.</p>
 <h3 id="tablet-merging-14">Tablet Merging (1.4)</h3>
 <p>Tablet merging is a new feature. Merging of tablets can be requested in the
-shell; Accumulo does not merge tablets automatically.</p>
+shell; Accumulo does not merge tablets automatically. In 1.5, the METADATA tablets 
+can be merged.</p>
 <h3 id="table-cloning-14">Table Cloning (1.4)</h3>
 <p>Allows users to quickly create a new table that references an existing table's
 data and copies its configuration. A cloned table and its source table can be