accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r956554 [3/4] - in /websites/staging/accumulo/trunk/content: ./ 1.4/examples/ 1.4/user_manual/ 1.5/examples/ 1.6/examples/ 1.7/examples/ downloads/ example/ governance/ release_notes/ user_manual_1.3-incubating/ user_manual_1.3-incubating/e...
Date Wed, 01 Jul 2015 15:34:50 GMT
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 Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>

Modified: websites/staging/accumulo/trunk/content/release_notes/index.html
==============================================================================
--- websites/staging/accumulo/trunk/content/release_notes/index.html (original)
+++ websites/staging/accumulo/trunk/content/release_notes/index.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -232,6 +233,7 @@ concerns) in updating to a new version.<
 </ul>
 <h3 id="16-releases">1.6 releases</h3>
 <ul>
+<li><a href="1.6.3.html">Apache Accumulo 1.6.3</a></li>
 <li><a href="1.6.2.html">Apache Accumulo 1.6.2</a></li>
 <li><a href="1.6.1.html">Apache Accumulo 1.6.1</a></li>
 <li><a href="1.6.0.html">Apache Accumulo 1.6.0</a></li>

Modified: websites/staging/accumulo/trunk/content/releasing.html
==============================================================================
--- websites/staging/accumulo/trunk/content/releasing.html (original)
+++ websites/staging/accumulo/trunk/content/releasing.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>

Modified: websites/staging/accumulo/trunk/content/screenshots.html
==============================================================================
--- websites/staging/accumulo/trunk/content/screenshots.html (original)
+++ websites/staging/accumulo/trunk/content/screenshots.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>

Modified: websites/staging/accumulo/trunk/content/source.html
==============================================================================
--- websites/staging/accumulo/trunk/content/source.html (original)
+++ websites/staging/accumulo/trunk/content/source.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Accumulo_Design.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Accumulo_Design.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Accumulo_Design.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -225,35 +226,35 @@ Latest 1.5 release: <strong>1.5.3</stron
 <li><a href="Accumulo_Design.html#Fault-Tolerance">Fault-Tolerance</a></li>
 </ul>
 <hr />
-<h2 id="wzxhzdk2wzxhzdk3-accumulo-design"><a id=Accumulo_Design></a> Accumulo Design</h2>
-<h2 id="wzxhzdk4wzxhzdk5-data-model"><a id=Data_Model></a> Data Model</h2>
+<h2 id="accumulo-design"><a id=Accumulo_Design></a> Accumulo Design</h2>
+<h2 id="data-model"><a id=Data_Model></a> Data Model</h2>
 <p>Accumulo provides a richer data model than simple key-value stores, but is not a fully relational database. Data is represented as key-value pairs, where the key and value are comprised of the following elements: </p>
 <p><img alt="converted table" src="img1.png" /></p>
 <p>All elements of the Key and the Value are represented as byte arrays except for Timestamp, which is a Long. Accumulo sorts keys by element and lexicographically in ascending order. Timestamps are sorted in descending order so that later versions of the same Key appear first in a sequential scan. Tables consist of a set of sorted key-value pairs. </p>
-<h2 id="wzxhzdk6wzxhzdk7-architecture"><a id=Architecture></a> Architecture</h2>
+<h2 id="architecture"><a id=Architecture></a> Architecture</h2>
 <p>Accumulo is a distributed data storage and retrieval system and as such consists of several architectural components, some of which run on many individual servers. Much of the work Accumulo does involves maintaining certain properties of the data, such as organization, availability, and integrity, across many commodity-class machines. </p>
-<h2 id="wzxhzdk8wzxhzdk9-components"><a id=Components></a> Components</h2>
+<h2 id="components"><a id=Components></a> Components</h2>
 <p>An instance of Accumulo includes many TabletServers, write-ahead Logger servers, one Garbage Collector process, one Master server and many Clients. </p>
-<h3 id="wzxhzdk10wzxhzdk11-tablet-server"><a id=Tablet_Server></a> Tablet Server</h3>
+<h3 id="tablet-server"><a id=Tablet_Server></a> Tablet Server</h3>
 <p>The TabletServer manages some subset of all the tablets (partitions of tables). This includes receiving writes from clients, persisting writes to a write‐ahead log, sorting new key‐value pairs in memory, periodically flushing sorted key‐value pairs to new files in HDFS, and responding to reads from clients, forming a merge‐sorted view of all keys and values from all the files it has created and the sorted in‐memory store. </p>
 <p>TabletServers also perform recovery of a tablet that was previously on a server that failed, reapplying any writes found in the write-ahead log to the tablet. </p>
-<h3 id="wzxhzdk12wzxhzdk13-loggers"><a id=Loggers></a> Loggers</h3>
+<h3 id="loggers"><a id=Loggers></a> Loggers</h3>
 <p>The Loggers accept updates to Tablet servers and write them to local on-disk storage. Each tablet server will write their updates to multiple loggers to preserve data in case of hardware failure. </p>
-<h3 id="wzxhzdk14wzxhzdk15-garbage-collector"><a id=Garbage_Collector></a> Garbage Collector</h3>
+<h3 id="garbage-collector"><a id=Garbage_Collector></a> Garbage Collector</h3>
 <p>Accumulo processes will share files stored in HDFS. Periodically, the Garbage Collector will identify files that are no longer needed by any process, and delete them. </p>
-<h3 id="wzxhzdk16wzxhzdk17-master"><a id=Master></a> Master</h3>
+<h3 id="master"><a id=Master></a> Master</h3>
 <p>The Accumulo Master is responsible for detecting and responding to TabletServer failure. It tries to balance the load across TabletServer by assigning tablets carefully and instructing TabletServers to migrate tablets when necessary. The Master ensures all tablets are assigned to one TabletServer each, and handles table creation, alteration, and deletion requests from clients. The Master also coordinates startup, graceful shutdown and recovery of changes in write-ahead logs when Tablet servers fail. </p>
-<h3 id="wzxhzdk18wzxhzdk19-client"><a id=Client></a> Client</h3>
+<h3 id="client"><a id=Client></a> Client</h3>
 <p>Accumulo includes a client library that is linked to every application. The client library contains logic for finding servers managing a particular tablet, and communicating with TabletServers to write and retrieve key-value pairs. </p>
-<h2 id="wzxhzdk20wzxhzdk21-data-management"><a id=Data_Management></a> Data Management</h2>
+<h2 id="data-management"><a id=Data_Management></a> Data Management</h2>
 <p>Accumulo stores data in tables, which are partitioned into tablets. Tablets are partitioned on row boundaries so that all of the columns and values for a particular row are found together within the same tablet. The Master assigns Tablets to one TabletServer at a time. This enables row-level transactions to take place without using distributed locking or some other complicated synchronization mechanism. As clients insert and query data, and as machines are added and removed from the cluster, the Master migrates tablets to ensure they remain available and that the ingest and query load is balanced across the cluster. </p>
 <p><img alt="Image data_distribution" src="./data_distribution.png" /></p>
-<h2 id="wzxhzdk22wzxhzdk23-tablet-service"><a id=Tablet_Service></a> Tablet Service</h2>
+<h2 id="tablet-service"><a id=Tablet_Service></a> Tablet Service</h2>
 <p>When a write arrives at a TabletServer it is written to a Write‐Ahead Log and then inserted into a sorted data structure in memory called a MemTable. When the MemTable reaches a certain size the TabletServer writes out the sorted key-value pairs to a file in HDFS called Indexed Sequential Access Method (ISAM) file. This process is called a minor compaction. A new MemTable is then created and the fact of the compaction is recorded in the Write‐Ahead Log. </p>
 <p>When a request to read data arrives at a TabletServer, the TabletServer does a binary search across the MemTable as well as the in-memory indexes associated with each ISAM file to find the relevant values. If clients are performing a scan, several key‐value pairs are returned to the client in order from the MemTable and the set of ISAM files by performing a merge‐sort as they are read. </p>
-<h2 id="wzxhzdk24wzxhzdk25-compactions"><a id=Compactions></a> Compactions</h2>
+<h2 id="compactions"><a id=Compactions></a> Compactions</h2>
 <p>In order to manage the number of files per tablet, periodically the TabletServer performs Major Compactions of files within a tablet, in which some set of ISAM files are combined into one file. The previous files will eventually be removed by the Garbage Collector. This also provides an opportunity to permanently remove deleted key‐value pairs by omitting key‐value pairs suppressed by a delete entry when the new file is created. </p>
-<h2 id="wzxhzdk26wzxhzdk27-fault-tolerance"><a id=Fault-Tolerance></a> Fault-Tolerance</h2>
+<h2 id="fault-tolerance"><a id=Fault-Tolerance></a> Fault-Tolerance</h2>
 <p>If a TabletServer fails, the Master detects it and automatically reassigns the tablets assigned from the failed server to other servers. Any key-value pairs that were in memory at the time the TabletServer are automatically reapplied from the Write-Ahead Log to prevent any loss of data. </p>
 <p>The Master will coordinate the copying of write-ahead logs to HDFS so the logs are available to all tablet servers. To make recovery efficient, the updates within a log are grouped by tablet. The sorting process can be performed by Hadoops MapReduce or the Logger server. TabletServers can quickly apply the mutations from the sorted logs that are destined for the tablets they have now been assigned. </p>
 <p>TabletServer failures are noted on the Master's monitor page, accessible via <br />

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Accumulo_Shell.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Accumulo_Shell.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Accumulo_Shell.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -221,7 +222,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 <li><a href="Accumulo_Shell.html#User_Administration">User Administration</a></li>
 </ul>
 <hr />
-<h2 id="wzxhzdk9wzxhzdk10-accumulo-shell"><a id=Accumulo_Shell></a> Accumulo Shell</h2>
+<h2 id="accumulo-shell"><a id=Accumulo_Shell></a> Accumulo Shell</h2>
 <p>Accumulo provides a simple shell that can be used to examine the contents and configuration settings of tables, apply individual mutations, and change configuration settings. </p>
 <p>The shell can be started by the following command: </p>
 <div class="codehilite"><pre>$<span class="n">ACCUMULO_HOME</span><span class="o">/</span><span class="n">bin</span><span class="o">/</span><span class="n">accumulo</span> <span class="n">shell</span> <span class="o">-</span><span class="n">u</span> <span class="p">[</span><span class="n">username</span><span class="p">]</span>
@@ -240,7 +241,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 </pre></div>
 
 
-<h2 id="wzxhzdk11wzxhzdk12-basic-administration"><a id=Basic_Administration></a> Basic Administration</h2>
+<h2 id="basic-administration"><a id=Basic_Administration></a> Basic Administration</h2>
 <p>The Accumulo shell can be used to create and delete tables, as well as to configure table and instance specific options. </p>
 <div class="codehilite"><pre><span class="n">root</span><span class="p">@</span><span class="n">myinstance</span><span class="o">&gt;</span> <span class="n">tables</span>
 <span class="sx">!METADATA</span>
@@ -274,7 +275,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 </pre></div>
 
 
-<h2 id="wzxhzdk13wzxhzdk14-table-maintenance"><a id=Table_Maintenance></a> Table Maintenance</h2>
+<h2 id="table-maintenance"><a id=Table_Maintenance></a> Table Maintenance</h2>
 <p>The <strong>compact</strong> command instructs Accumulo to schedule a compaction of the table during which files are consolidated and deleted entries are removed. </p>
 <div class="codehilite"><pre><span class="n">root</span><span class="p">@</span><span class="n">myinstance</span> <span class="n">mytable</span><span class="o">&gt;</span> <span class="n">compact</span> <span class="o">-</span><span class="n">t</span> <span class="n">mytable</span>
 07 16<span class="p">:</span>13<span class="p">:</span>53<span class="p">,</span>201 <span class="p">[</span><span class="n">shell</span><span class="p">.</span><span class="n">Shell</span><span class="p">]</span> <span class="n">INFO</span> <span class="p">:</span> <span class="n">Compaction</span> <span class="n">of</span> <span class="n">table</span> <span class="n">mytable</span>
@@ -289,7 +290,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 </pre></div>
 
 
-<h2 id="wzxhzdk15wzxhzdk16-user-administration"><a id=User_Administration></a> User Administration</h2>
+<h2 id="user-administration"><a id=User_Administration></a> User Administration</h2>
 <p>The Shell can be used to add, remove, and grant privileges to users. </p>
 <div class="codehilite"><pre><span class="n">root</span><span class="p">@</span><span class="n">myinstance</span> <span class="n">mytable</span><span class="o">&gt;</span> <span class="n">createuser</span> <span class="n">bob</span>
 <span class="n">Enter</span> <span class="n">new</span> <span class="n">password</span> <span class="k">for</span> <span class="s">&#39;bob&#39;</span><span class="p">:</span> <span class="o">*********</span>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Administration.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Administration.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Administration.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -228,25 +229,25 @@ Latest 1.5 release: <strong>1.5.3</stron
 <li><a href="Administration.html#Recovery">Recovery</a></li>
 </ul>
 <hr />
-<h2 id="wzxhzdk4wzxhzdk5-administration"><a id=Administration></a> Administration</h2>
-<h2 id="wzxhzdk6wzxhzdk7-hardware"><a id=Hardware></a> Hardware</h2>
+<h2 id="administration"><a id=Administration></a> Administration</h2>
+<h2 id="hardware"><a id=Hardware></a> Hardware</h2>
 <p>Because we are running essentially two or three systems simultaneously layered across the cluster: HDFS, Accumulo and MapReduce, it is typical for hardware to consist of 4 to 8 cores, and 8 to 32 GB RAM. This is so each running process can have at least one core and 2 - 4 GB each. </p>
 <p>One core running HDFS can typically keep 2 to 4 disks busy, so each machine may typically have as little as 2 x 300GB disks and as much as 4 x 1TB or 2TB disks. </p>
 <p>It is possible to do with less than this, such as with 1u servers with 2 cores and 4GB each, but in this case it is recommended to only run up to two processes per machine - i.e. DataNode and TabletServer or DataNode and MapReduce worker but not all three. The constraint here is having enough available heap space for all the processes on a machine. </p>
-<h2 id="wzxhzdk8wzxhzdk9-network"><a id=Network></a> Network</h2>
+<h2 id="network"><a id=Network></a> Network</h2>
 <p>Accumulo communicates via remote procedure calls over TCP/IP for both passing data and control messages. In addition, Accumulo uses HDFS clients to communicate with HDFS. To achieve good ingest and query performance, sufficient network bandwidth must be available between any two machines. </p>
-<h2 id="wzxhzdk10wzxhzdk11-installation"><a id=Installation></a> Installation</h2>
+<h2 id="installation"><a id=Installation></a> Installation</h2>
 <p>Choose a directory for the Accumulo installation. This directory will be referenced by the environment variable $ACCUMULO_HOME. Run the following: </p>
 <div class="codehilite"><pre>$ <span class="n">tar</span> <span class="n">xzf</span> $<span class="n">ACCUMULO_HOME</span><span class="o">/</span><span class="n">accumulo</span><span class="p">.</span><span class="n">tar</span><span class="p">.</span><span class="n">gz</span>
 </pre></div>
 
 
 <p>Repeat this step at each machine within the cluster. Usually all machines have the same $ACCUMULO_HOME. </p>
-<h2 id="wzxhzdk12wzxhzdk13-dependencies"><a id=Dependencies></a> Dependencies</h2>
+<h2 id="dependencies"><a id=Dependencies></a> Dependencies</h2>
 <p>Accumulo requires HDFS and ZooKeeper to be configured and running before starting. Password-less SSH should be configured between at least the Accumulo master and TabletServer machines. It is also a good idea to run Network Time Protocol (NTP) within the cluster to ensure nodes' clocks don't get too out of sync, which can cause problems with automatically timestamped data. Accumulo will remove from the set of TabletServers those machines whose times differ too much from the master's. </p>
-<h2 id="wzxhzdk14wzxhzdk15-configuration"><a id=Configuration></a> Configuration</h2>
+<h2 id="configuration"><a id=Configuration></a> Configuration</h2>
 <p>Accumulo is configured by editing several Shell and XML files found in $ACCUMULO_HOME/conf. The structure closely resembles Hadoop's configuration files. </p>
-<h3 id="wzxhzdk16wzxhzdk17-edit-confaccumulo-envsh"><a id=Edit_conf/accumulo-env.sh></a> Edit conf/accumulo-env.sh</h3>
+<h3 id="edit-confaccumulo-envsh"><a id=Edit_conf/accumulo-env.sh></a> Edit conf/accumulo-env.sh</h3>
 <p>Accumulo needs to know where to find the software it depends on. Edit accumuloenv. sh and specify the following: </p>
 <ol>
 <li>Enter the location of the installation directory of Accumulo for $ACCUMULO_HOME</li>
@@ -258,7 +259,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 <p>By default Accumulo TabletServers are set to use 1GB of memory. You may change this by altering the value of $ACCUMULO_TSERVER_OPTS. Note the syntax is that of the Java JVM command line options. This value should be less than the physical memory of the machines running TabletServers. </p>
 <p>There are similar options for the master's memory usage and the garbage collector process. Reduce these if they exceed the physical RAM of your hardware and increase them, within the bounds of the physical RAM, if a process fails because of insufficient memory. </p>
 <p>Note that you will be specifying the Java heap space in accumulo-env.sh. You should make sure that the total heap space used for the Accumulo tserver and the Hadoop DataNode and TaskTracker is less than the available memory on each slave node in the cluster. On large clusters, it is recommended that the Accumulo master, Hadoop NameNode, secondary NameNode, and Hadoop JobTracker all be run on separate machines to allow them to use more heap space. If you are running these on the same machine on a small cluster, likewise make sure their heap space settings fit within the available memory. </p>
-<h3 id="wzxhzdk18wzxhzdk19-cluster-specification"><a id=Cluster_Specification></a> Cluster Specification</h3>
+<h3 id="cluster-specification"><a id=Cluster_Specification></a> Cluster Specification</h3>
 <p>On the machine that will serve as the Accumulo master: </p>
 <ol>
 <li>Write the IP address or domain name of the Accumulo Master to the <br />
@@ -267,7 +268,7 @@ $ACCUMULO_HOME/conf/masters file. </li>
 $ACCUMULO_HOME/conf/slaves, one per line. </li>
 </ol>
 <p>Note that if using domain names rather than IP addresses, DNS must be configured properly for all machines participating in the cluster. DNS can be a confusing source of errors. </p>
-<h3 id="wzxhzdk20wzxhzdk21-accumulo-settings"><a id=Accumulo_Settings></a> Accumulo Settings</h3>
+<h3 id="accumulo-settings"><a id=Accumulo_Settings></a> Accumulo Settings</h3>
 <p>Specify appropriate values for the following settings in <br />
 $ACCUMULO_HOME/conf/accumulo-site.xml : </p>
 <div class="codehilite"><pre><span class="nt">&lt;property&gt;</span>
@@ -286,27 +287,27 @@ $ACCUMULO_HOME/conf/accumulo-site.xml :
 <p>This enables Accumulo to find ZooKeeper. Accumulo uses ZooKeeper to coordinate settings between processes and helps finalize TabletServer failure. </p>
 <p>Accumulo records all changes to tables to a write-ahead log before committing them to the table. The `walog' setting specifies the local directory on each machine to which write-ahead logs are written. This directory should exist on all machines acting as TabletServers. </p>
 <p>Some settings can be modified via the Accumulo shell and take effect immediately. However, any settings that should be persisted across system restarts must be recorded in the accumulo-site.xml file. </p>
-<h3 id="wzxhzdk22wzxhzdk23-deploy-configuration"><a id=Deploy_Configuration></a> Deploy Configuration</h3>
+<h3 id="deploy-configuration"><a id=Deploy_Configuration></a> Deploy Configuration</h3>
 <p>Copy the masters, slaves, accumulo-env.sh, and if necessary, accumulo-site.xml from the <br />
 $ACCUMULO_HOME/conf/ directory on the master to all the machines specified in the slaves file. </p>
-<h2 id="wzxhzdk24wzxhzdk25-initialization"><a id=Initialization></a> Initialization</h2>
+<h2 id="initialization"><a id=Initialization></a> Initialization</h2>
 <p>Accumulo must be initialized to create the structures it uses internally to locate data across the cluster. HDFS is required to be configured and running before Accumulo can be initialized. </p>
 <p>Once HDFS is started, initialization can be performed by executing <br />
 $ACCUMULO_HOME/bin/accumulo init . This script will prompt for a name for this instance of Accumulo. The instance name is used to identify a set of tables and instance-specific settings. The script will then write some information into HDFS so Accumulo can start properly. </p>
 <p>The initialization script will prompt you to set a root password. Once Accumulo is initialized it can be started. </p>
-<h2 id="wzxhzdk26wzxhzdk27-running"><a id=Running></a> Running</h2>
-<h3 id="wzxhzdk28wzxhzdk29-starting-accumulo"><a id=Starting_Accumulo></a> Starting Accumulo</h3>
+<h2 id="running"><a id=Running></a> Running</h2>
+<h3 id="starting-accumulo"><a id=Starting_Accumulo></a> Starting Accumulo</h3>
 <p>Make sure Hadoop is configured on all of the machines in the cluster, including access to a shared HDFS instance. Make sure HDFS and ZooKeeper are running. Make sure ZooKeeper is configured and running on at least one machine in the cluster. Start Accumulo using the bin/start-all.sh script. </p>
 <p>To verify that Accumulo is running, check the Status page as described under <em>Monitoring</em>. In addition, the Shell can provide some information about the status of tables via reading the !METADATA table. </p>
-<h3 id="wzxhzdk30wzxhzdk31-stopping-accumulo"><a id=Stopping_Accumulo></a> Stopping Accumulo</h3>
+<h3 id="stopping-accumulo"><a id=Stopping_Accumulo></a> Stopping Accumulo</h3>
 <p>To shutdown cleanly, run bin/stop-all.sh and the master will orchestrate the shutdown of all the tablet servers. Shutdown waits for all minor compactions to finish, so it may take some time for particular configurations. </p>
-<h2 id="wzxhzdk32wzxhzdk33-monitoring"><a id=Monitoring></a> Monitoring</h2>
+<h2 id="monitoring"><a id=Monitoring></a> Monitoring</h2>
 <p>The Accumulo Master provides an interface for monitoring the status and health of Accumulo components. This interface can be accessed by pointing a web browser to <br />
 http://accumulomaster:50095/status</p>
-<h2 id="wzxhzdk34wzxhzdk35-logging"><a id=Logging></a> Logging</h2>
+<h2 id="logging"><a id=Logging></a> Logging</h2>
 <p>Accumulo processes each write to a set of log files. By default these are found under <br />
 $ACCUMULO/logs/. </p>
-<h2 id="wzxhzdk36wzxhzdk37-recovery"><a id=Recovery></a> Recovery</h2>
+<h2 id="recovery"><a id=Recovery></a> Recovery</h2>
 <p>In the event of TabletServer failure or error on shutting Accumulo down, some mutations may not have been minor compacted to HDFS properly. In this case, Accumulo will automatically reapply such mutations from the write-ahead log either when the tablets from the failed server are reassigned by the Master, in the case of a single TabletServer failure or the next time Accumulo starts, in the event of failure during shutdown. </p>
 <p>Recovery is performed by asking the loggers to copy their write-ahead logs into HDFS. As the logs are copied, they are also sorted, so that tablets can easily find their missing updates. The copy/sort status of each file is displayed on Accumulo monitor status page. Once the recovery is complete any tablets involved should return to an ``online" state. Until then those tablets will be unavailable to clients. </p>
 <p>The Accumulo client library is configured to retry failed mutations and in many cases clients will be able to continue processing after the recovery process without throwing an exception. </p>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Analytics.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Analytics.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Analytics.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -221,16 +222,16 @@ Latest 1.5 release: <strong>1.5.3</stron
 <li><a href="Analytics.html#Statistical_Modeling">Statistical Modeling</a></li>
 </ul>
 <hr />
-<h2 id="wzxhzdk10wzxhzdk11-analytics"><a id=Analytics></a> Analytics</h2>
+<h2 id="analytics"><a id=Analytics></a> Analytics</h2>
 <p>Accumulo supports more advanced data processing than simply keeping keys sorted and performing efficient lookups. Analytics can be developed by using MapReduce and Iterators in conjunction with Accumulo tables. </p>
-<h2 id="wzxhzdk12wzxhzdk13-mapreduce"><a id=MapReduce></a> MapReduce</h2>
+<h2 id="mapreduce"><a id=MapReduce></a> MapReduce</h2>
 <p>Accumulo tables can be used as the source and destination of MapReduce jobs. To use an Accumulo table with a MapReduce job (specifically with the new Hadoop API as of version 0.20), configure the job parameters to use the AccumuloInputFormat and AccumuloOutputFormat. Accumulo specific parameters can be set via these two format classes to do the following: </p>
 <ul>
 <li>Authenticate and provide user credentials for the input </li>
 <li>Restrict the scan to a range of rows </li>
 <li>Restrict the input to a subset of available columns </li>
 </ul>
-<h3 id="wzxhzdk14wzxhzdk15-mapper-and-reducer-classes"><a id=Mapper_and_Reducer_classes></a> Mapper and Reducer classes</h3>
+<h3 id="mapper-and-reducer-classes"><a id=Mapper_and_Reducer_classes></a> Mapper and Reducer classes</h3>
 <p>To read from an Accumulo table create a Mapper with the following class parameterization and be sure to configure the AccumuloInputFormat. </p>
 <div class="codehilite"><pre><span class="n">class</span> <span class="n">MyMapper</span> <span class="n">extends</span> <span class="n">Mapper</span><span class="o">&lt;</span><span class="n">Key</span><span class="p">,</span><span class="n">Value</span><span class="p">,</span><span class="n">WritableComparable</span><span class="p">,</span><span class="n">Writable</span><span class="o">&gt;</span> <span class="p">{</span>
     <span class="n">public</span> <span class="n">void</span> <span class="n">map</span><span class="p">(</span><span class="n">Key</span> <span class="n">k</span><span class="p">,</span> <span class="n">Value</span> <span class="n">v</span><span class="p">,</span> <span class="n">Context</span> <span class="n">c</span><span class="p">)</span> <span class="p">{</span>
@@ -256,7 +257,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 
 
 <p>The Text object passed as the output should contain the name of the table to which this mutation should be applied. The Text can be null in which case the mutation will be applied to the default table name specified in the AccumuloOutputFormat options. </p>
-<h3 id="wzxhzdk16wzxhzdk17-accumuloinputformat-options"><a id=AccumuloInputFormat_options></a> AccumuloInputFormat options</h3>
+<h3 id="accumuloinputformat-options"><a id=AccumuloInputFormat_options></a> AccumuloInputFormat options</h3>
 <div class="codehilite"><pre><span class="n">Job</span> <span class="n">job</span> <span class="p">=</span> <span class="n">new</span> <span class="n">Job</span><span class="p">(</span><span class="n">getConf</span><span class="p">());</span>
 <span class="n">AccumuloInputFormat</span><span class="p">.</span><span class="n">setInputInfo</span><span class="p">(</span><span class="n">job</span><span class="p">,</span>
         &quot;<span class="n">user</span>&quot;<span class="p">,</span>
@@ -289,7 +290,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 </pre></div>
 
 
-<h3 id="wzxhzdk18wzxhzdk19-accumulooutputformat-options"><a id=AccumuloOutputFormat_options></a> AccumuloOutputFormat options</h3>
+<h3 id="accumulooutputformat-options"><a id=AccumuloOutputFormat_options></a> AccumuloOutputFormat options</h3>
 <div class="codehilite"><pre><span class="n">boolean</span> <span class="n">createTables</span> <span class="p">=</span> <span class="n">true</span><span class="p">;</span>
 <span class="n">String</span> <span class="n">defaultTable</span> <span class="p">=</span> &quot;<span class="n">mytable</span>&quot;<span class="p">;</span>
 
@@ -312,13 +313,13 @@ Latest 1.5 release: <strong>1.5.3</stron
 
 <p>An example of using MapReduce with Accumulo can be found at <br />
 accumulo/docs/examples/README.mapred </p>
-<h2 id="wzxhzdk20wzxhzdk21-aggregating-iterators"><a id=Aggregating_Iterators></a> Aggregating Iterators</h2>
+<h2 id="aggregating-iterators"><a id=Aggregating_Iterators></a> Aggregating Iterators</h2>
 <p>Many applications can benefit from the ability to aggregate values across common keys. This can be done via aggregating iterators and is similar to the Reduce step in MapReduce. This provides the ability to define online, incrementally updated analytics without the overhead or latency associated with batch-oriented MapReduce jobs. </p>
 <p>All that is needed to aggregate values of a table is to identify the fields over which values will be grouped, insert mutations with those fields as the key, and configure the table with an aggregating iterator that supports the summarization operation desired. </p>
 <p>The only restriction on an aggregating iterator is that the aggregator developer should not assume that all values for a given key have been seen, since new mutations can be inserted at anytime. This precludes using the total number of values in the aggregation such as when calculating an average, for example. </p>
-<h3 id="wzxhzdk22wzxhzdk23-feature-vectors"><a id=Feature_Vectors></a> Feature Vectors</h3>
+<h3 id="feature-vectors"><a id=Feature_Vectors></a> Feature Vectors</h3>
 <p>An interesting use of aggregating iterators within an Accumulo table is to store feature vectors for use in machine learning algorithms. For example, many algorithms such as k-means clustering, support vector machines, anomaly detection, etc. use the concept of a feature vector and the calculation of distance metrics to learn a particular model. The columns in an Accumulo table can be used to efficiently store sparse features and their weights to be incrementally updated via the use of an aggregating iterator. </p>
-<h2 id="wzxhzdk24wzxhzdk25-statistical-modeling"><a id=Statistical_Modeling></a> Statistical Modeling</h2>
+<h2 id="statistical-modeling"><a id=Statistical_Modeling></a> Statistical Modeling</h2>
 <p>Statistical models that need to be updated by many machines in parallel could be similarly stored within an Accumulo table. For example, a MapReduce job that is iteratively updating a global statistical model could have each map or reduce worker reference the parts of the model to be read and updated through an embedded Accumulo client. </p>
 <p>Using Accumulo this way enables efficient and fast lookups and updates of small pieces of information in a random access pattern, which is complementary to MapReduce's sequential access model. </p>
 <hr />

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Contents.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Contents.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Contents.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -214,7 +215,7 @@ Latest 1.5 release: <strong>1.5.3</stron
     <h1 class="title">Apache Accumulo User Manual: Contents</h1>
 
     <p><strong> Next:</strong> <a href="Introduction.html">Introduction</a> <strong> Up:</strong> <a href="accumulo_user_manual.html">Apache Accumulo User Manual Version 1.3</a> <strong> Previous:</strong> <a href="accumulo_user_manual.html">Apache Accumulo User Manual Version 1.3</a>   </p>
-<h3 id="wzxhzdk0wzxhzdk1-contents"><a id=Contents></a> Contents</h3>
+<h3 id="contents"><a id=Contents></a> Contents</h3>
 <ul>
 <li><a href="Introduction.html">Introduction</a></li>
 <li>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/High_Speed_Ingest.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/High_Speed_Ingest.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/High_Speed_Ingest.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -222,9 +223,9 @@ Latest 1.5 release: <strong>1.5.3</stron
 <li><a href="High_Speed_Ingest.html#MapReduce_Ingest">MapReduce Ingest</a></li>
 </ul>
 <hr />
-<h2 id="wzxhzdk5wzxhzdk6-high-speed-ingest"><a id=High-Speed_Ingest></a> High-Speed Ingest</h2>
+<h2 id="high-speed-ingest"><a id=High-Speed_Ingest></a> High-Speed Ingest</h2>
 <p>Accumulo is often used as part of a larger data processing and storage system. To maximize the performance of a parallel system involving Accumulo, the ingestion and query components should be designed to provide enough parallelism and concurrency to avoid creating bottlenecks for users and other systems writing to and reading from Accumulo. There are several ways to achieve high ingest performance. </p>
-<h2 id="wzxhzdk7wzxhzdk8-pre-splitting-new-tables"><a id=Pre-Splitting_New_Tables></a> Pre-Splitting New Tables</h2>
+<h2 id="pre-splitting-new-tables"><a id=Pre-Splitting_New_Tables></a> Pre-Splitting New Tables</h2>
 <p>New tables consist of a single tablet by default. As mutations are applied, the table grows and splits into multiple tablets which are balanced by the Master across TabletServers. This implies that the aggregate ingest rate will be limited to fewer servers than are available within the cluster until the table has reached the point where there are tablets on every TabletServer. </p>
 <p>Pre-splitting a table ensures that there are as many tablets as desired available before ingest begins to take advantage of all the parallelism possible with the cluster hardware. Tables can be split anytime by using the shell: </p>
 <div class="codehilite"><pre><span class="n">user</span><span class="p">@</span><span class="n">myinstance</span> <span class="n">mytable</span><span class="o">&gt;</span> <span class="n">addsplits</span> <span class="o">-</span><span class="n">sf</span> <span class="o">/</span><span class="n">local_splitfile</span> <span class="o">-</span><span class="n">t</span> <span class="n">mytable</span>
@@ -232,10 +233,10 @@ Latest 1.5 release: <strong>1.5.3</stron
 
 
 <p>For the purposes of providing parallelism to ingest it is not necessary to create more tablets than there are physical machines within the cluster as the aggregate ingest rate is a function of the number of physical machines. Note that the aggregate ingest rate is still subject to the number of machines running ingest clients, and the distribution of rowIDs across the table. The aggregation ingest rate will be suboptimal if there are many inserts into a small number of rowIDs. </p>
-<h2 id="wzxhzdk9wzxhzdk10-multiple-ingester-clients"><a id=Multiple_Ingester_Clients></a> Multiple Ingester Clients</h2>
+<h2 id="multiple-ingester-clients"><a id=Multiple_Ingester_Clients></a> Multiple Ingester Clients</h2>
 <p>Accumulo is capable of scaling to very high rates of ingest, which is dependent upon not just the number of TabletServers in operation but also the number of ingest clients. This is because a single client, while capable of batching mutations and sending them to all TabletServers, is ultimately limited by the amount of data that can be processed on a single machine. The aggregate ingest rate will scale linearly with the number of clients up to the point at which either the aggregate I/O of TabletServers or total network bandwidth capacity is reached. </p>
 <p>In operational settings where high rates of ingest are paramount, clusters are often configured to dedicate some number of machines solely to running Ingester Clients. The exact ratio of clients to TabletServers necessary for optimum ingestion rates will vary according to the distribution of resources per machine and by data type. </p>
-<h2 id="wzxhzdk11wzxhzdk12-bulk-ingest"><a id=Bulk_Ingest></a> Bulk Ingest</h2>
+<h2 id="bulk-ingest"><a id=Bulk_Ingest></a> Bulk Ingest</h2>
 <p>Accumulo supports the ability to import files produced by an external process such as MapReduce into an existing table. In some cases it may be faster to load data this way rather than via ingesting through clients using BatchWriters. This allows a large number of machines to format data the way Accumulo expects. The new files can then simply be introduced to Accumulo via a shell command. </p>
 <p>To configure MapReduce to format data in preparation for bulk loading, the job should be set to use a range partitioner instead of the default hash partitioner. The range partitioner uses the split points of the Accumulo table that will receive the data. The split points can be obtained from the shell and used by the MapReduce RangePartitioner. Note that this is only useful if the existing table is already split into multiple tablets. </p>
 <div class="codehilite"><pre><span class="n">user</span><span class="p">@</span><span class="n">myinstance</span> <span class="n">mytable</span><span class="o">&gt;</span> <span class="n">getsplits</span>
@@ -257,7 +258,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 <p>Note that the paths referenced are directories within the same HDFS instance over which Accumulo is running. Accumulo places any files that failed to be added to the second directory specified. </p>
 <p>A complete example of using Bulk Ingest can be found at <br />
 accumulo/docs/examples/README.bulkIngest </p>
-<h2 id="wzxhzdk13wzxhzdk14-mapreduce-ingest"><a id=MapReduce_Ingest></a> MapReduce Ingest</h2>
+<h2 id="mapreduce-ingest"><a id=MapReduce_Ingest></a> MapReduce Ingest</h2>
 <p>It is possible to efficiently write many mutations to Accumulo in parallel via a MapReduce job. In this scenario the MapReduce is written to process data that lives in HDFS and write mutations to Accumulo using the AccumuloOutputFormat. See the MapReduce section under Analytics for details. </p>
 <p>An example of using MapReduce can be found under <br />
 accumulo/docs/examples/README.mapred </p>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Introduction.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Introduction.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Introduction.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -214,7 +215,7 @@ Latest 1.5 release: <strong>1.5.3</stron
     <h1 class="title">Apache Accumulo User Manual: Introduction</h1>
 
     <p><strong> Next:</strong> <a href="Accumulo_Design.html">Accumulo Design</a> <strong> Up:</strong> <a href="accumulo_user_manual.html">Apache Accumulo User Manual Version 1.3</a> <strong> Previous:</strong> <a href="Contents.html">Contents</a>   <strong> <a href="Contents.html">Contents</a></strong>   </p>
-<h2 id="wzxhzdk0wzxhzdk1-introduction"><a id=Introduction></a> Introduction</h2>
+<h2 id="introduction"><a id=Introduction></a> Introduction</h2>
 <p>Apache Accumulo is a highly scalable structured store based on Google's BigTable. Accumulo is written in Java and operates over the Hadoop Distributed File System (HDFS), which is part of the popular Apache Hadoop project. Accumulo supports efficient storage and retrieval of structured data, including queries for ranges, and provides support for using Accumulo tables as input and output for MapReduce jobs. </p>
 <p>Accumulo features automatic load-balancing and partitioning, data compression and fine-grained security labels. </p>
 <hr />

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Security.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Security.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Security.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -223,9 +224,9 @@ Latest 1.5 release: <strong>1.5.3</stron
 <li><a href="Security.html#Query_Services_Layer">Query Services Layer</a></li>
 </ul>
 <hr />
-<h2 id="wzxhzdk6wzxhzdk7-security"><a id=Security></a> Security</h2>
+<h2 id="security"><a id=Security></a> Security</h2>
 <p>Accumulo extends the BigTable data model to implement a security mechanism known as cell-level security. Every key-value pair has its own security label, stored under the column visibility element of the key, which is used to determine whether a given user meets the security requirements to read the value. This enables data of various security levels to be stored within the same row, and users of varying degrees of access to query the same table, while preserving data confidentiality. </p>
-<h2 id="wzxhzdk8wzxhzdk9-security-label-expressions"><a id=Security_Label_Expressions></a> Security Label Expressions</h2>
+<h2 id="security-label-expressions"><a id=Security_Label_Expressions></a> Security Label Expressions</h2>
 <p>When mutations are applied, users can specify a security label for each value. This is done as the Mutation is created by passing a ColumnVisibility object to the put() method: </p>
 <div class="codehilite"><pre><span class="n">Text</span> <span class="n">rowID</span> <span class="p">=</span> <span class="n">new</span> <span class="n">Text</span><span class="p">(</span>&quot;<span class="n">row1</span>&quot;<span class="p">);</span>
 <span class="n">Text</span> <span class="n">colFam</span> <span class="p">=</span> <span class="n">new</span> <span class="n">Text</span><span class="p">(</span>&quot;<span class="n">myColFam</span>&quot;<span class="p">);</span>
@@ -240,7 +241,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 </pre></div>
 
 
-<h2 id="wzxhzdk10wzxhzdk11-security-label-expression-syntax"><a id=Security_Label_Expression_Syntax></a> Security Label Expression Syntax</h2>
+<h2 id="security-label-expression-syntax"><a id=Security_Label_Expression_Syntax></a> Security Label Expression Syntax</h2>
 <p>Security labels consist of a set of user-defined tokens that are required to read the value the label is associated with. The set of tokens required can be specified using syntax that supports logical AND and OR combinations of tokens, as well as nesting groups of tokens together. </p>
 <p>For example, suppose within our organization we want to label our data values with security labels defined in terms of user roles. We might have tokens such as: </p>
 <div class="codehilite"><pre><span class="n">admin</span>
@@ -265,7 +266,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 
 
 <p>When both <code>|</code> and <code>&amp;</code> operators are used, parentheses must be used to specify precedence of the operators. </p>
-<h2 id="wzxhzdk12wzxhzdk13-authorization"><a id=Authorization></a> Authorization</h2>
+<h2 id="authorization"><a id=Authorization></a> Authorization</h2>
 <p>When clients attempt to read data from Accumulo, any security labels present are examined against the set of authorizations passed by the client code when the Scanner or BatchScanner are created. If the authorizations are determined to be insufficient to satisfy the security label, the value is suppressed from the set of results sent back to the client. </p>
 <p>Authorizations are specified as a comma-separated list of tokens the user possesses: </p>
 <div class="codehilite"><pre><span class="c1">// user possess both admin and system level access</span>
@@ -275,10 +276,10 @@ Latest 1.5 release: <strong>1.5.3</stron
 </pre></div>
 
 
-<h2 id="wzxhzdk14wzxhzdk15-secure-authorizations-handling"><a id=Secure_Authorizations_Handling></a> Secure Authorizations Handling</h2>
+<h2 id="secure-authorizations-handling"><a id=Secure_Authorizations_Handling></a> Secure Authorizations Handling</h2>
 <p>Because the client can pass any authorization tokens to Accumulo, applications must be designed to obtain users' authorization tokens from a trusted 3rd party rather than having the users specify their authorizations directly. </p>
 <p>Often production systems will integrate with Public-Key Infrastructure (PKI) and designate client code within the query layer to negotiate with PKI servers in order to authenticate users and retrieve their authorization tokens (credentials). This requires users to specify only the information necessary to authenticate themselves to the system. Once user identity is established, their credentials can be accessed by the client code and passed to Accumulo outside of the reach of the user. </p>
-<h2 id="wzxhzdk16wzxhzdk17-query-services-layer"><a id=Query_Services_Layer></a> Query Services Layer</h2>
+<h2 id="query-services-layer"><a id=Query_Services_Layer></a> Query Services Layer</h2>
 <p>Since the primary method of interaction with Accumulo is through the Java API, production environments often call for the implementation of a Query layer. This can be done using web services in containers such as Apache Tomcat, but is not a requirement. The Query Services Layer provides a mechanism for providing a platform on which user facing applications can be built. This allows the application designers to isolate potentially complex query logic, and enables a convenient point at which to perform essential security functions. </p>
 <p>Several production environments choose to implement authentication at this layer, where users identifiers are used to retrieve their access credentials which are then cached within the query layer and presented to Accumulo through the Authorizations mechanism. </p>
 <p>Typically, the query services layer sits between Accumulo and user workstations. </p>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Shell_Commands.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Shell_Commands.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Shell_Commands.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -214,7 +215,7 @@ Latest 1.5 release: <strong>1.5.3</stron
     <h1 class="title">Apache Accumulo User Manual: Shell Commands</h1>
 
     <p><strong> Up:</strong> <a href="accumulo_user_manual.html">Apache Accumulo User Manual Version 1.3</a> <strong> Previous:</strong> <a href="Administration.html">Administration</a>   <strong> <a href="Contents.html">Contents</a></strong>   </p>
-<h2 id="wzxhzdk59wzxhzdk60-shell-commands"><a id=Shell_Commands></a> Shell Commands</h2>
+<h2 id="shell-commands"><a id=Shell_Commands></a> Shell Commands</h2>
 <p><strong>?</strong>   </p>
 <div class="codehilite"><pre><span class="n">usage</span><span class="p">:</span> ? <span class="p">[</span> <span class="o">&lt;</span><span class="n">command</span><span class="o">&gt;</span> <span class="o">&lt;</span><span class="n">command</span><span class="o">&gt;</span> <span class="p">]</span> <span class="p">[</span><span class="o">-</span>?<span class="p">]</span> <span class="p">[</span><span class="o">-</span><span class="n">np</span><span class="p">]</span>   
 <span class="n">description</span><span class="p">:</span> <span class="n">provides</span> <span class="n">information</span> <span class="n">about</span> <span class="n">the</span> <span class="n">available</span> <span class="n">commands</span>   

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Table_Configuration.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Table_Configuration.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Table_Configuration.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -224,12 +225,12 @@ Latest 1.5 release: <strong>1.5.3</stron
 <li><a href="Table_Configuration.html#Block_Cache">Block Cache</a></li>
 </ul>
 <hr />
-<h2 id="wzxhzdk19wzxhzdk20-table-configuration"><a id=Table_Configuration></a> Table Configuration</h2>
+<h2 id="table-configuration"><a id=Table_Configuration></a> Table Configuration</h2>
 <p>Accumulo tables have a few options that can be configured to alter the default behavior of Accumulo as well as improve performance based on the data stored. These include locality groups, constraints, and iterators. </p>
-<h2 id="wzxhzdk21wzxhzdk22-locality-groups"><a id=Locality_Groups></a> Locality Groups</h2>
+<h2 id="locality-groups"><a id=Locality_Groups></a> Locality Groups</h2>
 <p>Accumulo supports storing of sets of column families separately on disk to allow clients to scan over columns that are frequently used together efficient and to avoid scanning over column families that are not requested. After a locality group is set Scanner and BatchScanner operations will automatically take advantage of them whenever the fetchColumnFamilies() method is used. </p>
 <p>By default tables place all column families into the same ``default" locality group. Additional locality groups can be configured anytime via the shell or programmatically as follows: </p>
-<h3 id="wzxhzdk23wzxhzdk24-managing-locality-groups-via-the-shell"><a id=Managing_Locality_Groups_via_the_Shell></a> Managing Locality Groups via the Shell</h3>
+<h3 id="managing-locality-groups-via-the-shell"><a id=Managing_Locality_Groups_via_the_Shell></a> Managing Locality Groups via the Shell</h3>
 <div class="codehilite"><pre><span class="n">usage</span><span class="o">:</span> <span class="n">setgroups</span> <span class="o">&lt;</span><span class="n">group</span><span class="o">&gt;=&lt;</span><span class="n">col</span> <span class="n">fam</span><span class="o">&gt;{,&lt;</span><span class="n">col</span> <span class="n">fam</span><span class="o">&gt;}{</span> <span class="o">&lt;</span><span class="n">group</span><span class="o">&gt;=&lt;</span><span class="n">col</span> <span class="n">fam</span><span class="o">&gt;{,&lt;</span><span class="n">col</span>
 <span class="n">fam</span><span class="o">&gt;}}</span> <span class="o">[-?]</span> <span class="o">-</span><span class="n">t</span> <span class="o">&lt;</span><span class="n">table</span><span class="o">&gt;</span>
 
@@ -240,7 +241,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 </pre></div>
 
 
-<h3 id="wzxhzdk25wzxhzdk26-managing-locality-groups-via-the-client-api"><a id=Managing_Locality_Groups_via_the_Client_API></a> Managing Locality Groups via the Client API</h3>
+<h3 id="managing-locality-groups-via-the-client-api"><a id=Managing_Locality_Groups_via_the_Client_API></a> Managing Locality Groups via the Client API</h3>
 <div class="codehilite"><pre><span class="n">Connector</span> <span class="n">conn</span><span class="p">;</span>
 
 <span class="n">HashMap</span><span class="o">&lt;</span><span class="n">String</span><span class="p">,</span><span class="n">Set</span><span class="o">&lt;</span><span class="n">Text</span><span class="o">&gt;&gt;</span> <span class="n">localityGroups</span> <span class="p">=</span>
@@ -270,7 +271,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 </pre></div>
 
 
-<h2 id="wzxhzdk27wzxhzdk28-constraints"><a id=Constraints></a> Constraints</h2>
+<h2 id="constraints"><a id=Constraints></a> Constraints</h2>
 <p>Accumulo supports constraints applied on mutations at insert time. This can be used to disallow certain inserts according to a user defined policy. Any mutation that fails to meet the requirements of the constraint is rejected and sent back to the client. </p>
 <p>Constraints can be enabled by setting a table property as follows: </p>
 <div class="codehilite"><pre><span class="n">user</span><span class="p">@</span><span class="n">myinstance</span> <span class="n">mytable</span><span class="o">&gt;</span> <span class="n">config</span> <span class="o">-</span><span class="n">t</span> <span class="n">mytable</span> <span class="o">-</span><span class="n">s</span> <span class="n">table</span><span class="p">.</span><span class="n">constraint</span><span class="p">.</span>1<span class="p">=</span><span class="n">com</span><span class="p">.</span><span class="n">test</span><span class="p">.</span><span class="n">ExampleConstraint</span>
@@ -290,7 +291,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 <p>An example of constraints can be found in <br />
 accumulo/docs/examples/README.constraints with corresponding code under <br />
 accumulo/src/examples/main/java/accumulo/examples/constraints . </p>
-<h2 id="wzxhzdk29wzxhzdk30-bloom-filters"><a id=Bloom_Filters></a> Bloom Filters</h2>
+<h2 id="bloom-filters"><a id=Bloom_Filters></a> Bloom Filters</h2>
 <p>As mutations are applied to an Accumulo table, several files are created per tablet. If bloom filters are enabled, Accumulo will create and load a small data structure into memory to determine whether a file contains a given key before opening the file. This can speed up lookups considerably. </p>
 <p>To enable bloom filters, enter the following command in the Shell: </p>
 <div class="codehilite"><pre><span class="n">user</span><span class="p">@</span><span class="n">myinstance</span><span class="o">&gt;</span> <span class="n">config</span> <span class="o">-</span><span class="n">t</span> <span class="n">mytable</span> <span class="o">-</span><span class="n">s</span> <span class="n">table</span><span class="p">.</span><span class="n">bloom</span><span class="p">.</span><span class="n">enabled</span><span class="p">=</span><span class="n">true</span>
@@ -299,9 +300,9 @@ accumulo/src/examples/main/java/accumulo
 
 <p>An extensive example of using Bloom Filters can be found at <br />
 accumulo/docs/examples/README.bloom . </p>
-<h2 id="wzxhzdk31wzxhzdk32-iterators"><a id=Iterators></a> Iterators</h2>
+<h2 id="iterators"><a id=Iterators></a> Iterators</h2>
 <p>Iterators provide a modular mechanism for adding functionality to be executed by TabletServers when scanning or compacting data. This allows users to efficiently summarize, filter, and aggregate data. In fact, the built-in features of cell-level security and age-off are implemented using Iterators. </p>
-<h3 id="wzxhzdk33wzxhzdk34-setting-iterators-via-the-shell"><a id=Setting_Iterators_via_the_Shell></a> Setting Iterators via the Shell</h3>
+<h3 id="setting-iterators-via-the-shell"><a id=Setting_Iterators_via_the_Shell></a> Setting Iterators via the Shell</h3>
 <div class="codehilite"><pre><span class="n">usage</span><span class="o">:</span> <span class="n">setiter</span> <span class="o">[-?]</span> <span class="o">-</span><span class="n">agg</span> <span class="o">|</span> <span class="o">-</span><span class="kd">class</span> <span class="o">&lt;</span><span class="n">name</span><span class="o">&gt;</span> <span class="o">|</span> <span class="o">-</span><span class="n">filter</span> <span class="o">|</span> <span class="o">-</span><span class="n">nolabel</span> <span class="o">|</span> 
 <span class="o">-</span><span class="n">regex</span> <span class="o">|</span> <span class="o">-</span><span class="n">vers</span> <span class="o">[-</span><span class="n">majc</span><span class="o">]</span> <span class="o">[-</span><span class="n">minc</span><span class="o">]</span> <span class="o">[-</span><span class="n">n</span> <span class="o">&lt;</span><span class="n">itername</span><span class="o">&gt;]</span> <span class="o">-</span><span class="n">p</span> <span class="o">&lt;</span><span class="n">pri</span><span class="o">&gt;</span> <span class="o">[-</span><span class="n">scan</span><span class="o">]</span> 
 <span class="o">[-</span><span class="n">t</span> <span class="o">&lt;</span><span class="n">table</span><span class="o">&gt;]</span>
@@ -310,7 +311,7 @@ accumulo/docs/examples/README.bloom . </
 </pre></div>
 
 
-<h3 id="wzxhzdk35wzxhzdk36-setting-iterators-programmatically"><a id=Setting_Iterators_Programmatically></a> Setting Iterators Programmatically</h3>
+<h3 id="setting-iterators-programmatically"><a id=Setting_Iterators_Programmatically></a> Setting Iterators Programmatically</h3>
 <div class="codehilite"><pre><span class="n">scanner</span><span class="p">.</span><span class="n">setScanIterators</span><span class="p">(</span>
     15<span class="p">,</span> <span class="o">//</span> <span class="n">priority</span>
     &quot;<span class="n">com</span><span class="p">.</span><span class="n">company</span><span class="p">.</span><span class="n">MyIterator</span>&quot;<span class="p">,</span> <span class="o">//</span> <span class="n">class</span> <span class="n">name</span>
@@ -327,7 +328,7 @@ accumulo/docs/examples/README.bloom . </
 
 
 <p>Tables support separate Iterator settings to be applied at scan time, upon minor compaction and upon major compaction. For most uses, tables will have identical iterator settings for all three to avoid inconsistent results. </p>
-<h3 id="wzxhzdk37wzxhzdk38-versioning-iterators-and-timestamps"><a id=Versioning_Iterators_and_Timestamps></a> Versioning Iterators and Timestamps</h3>
+<h3 id="versioning-iterators-and-timestamps"><a id=Versioning_Iterators_and_Timestamps></a> Versioning Iterators and Timestamps</h3>
 <p>Accumulo provides the capability to manage versioned data through the use of timestamps within the Key. If a timestamp is not specified in the key created by the client then the system will set the timestamp to the current time. Two keys with identical rowIDs and columns but different timestamps are considered two versions of the same key. If two inserts are made into accumulo with the same rowID, column, and timestamp, then the behavior is non-deterministic. </p>
 <p>Timestamps are sorted in descending order, so the most recent data comes first. Accumulo can be configured to return the top k versions, or versions later than a given date. The default is to return the one most recent version. </p>
 <p>The version policy can be changed by changing the VersioningIterator options for a table as follows: </p>
@@ -342,16 +343,16 @@ accumulo/docs/examples/README.bloom . </
 </pre></div>
 
 
-<h4 id="wzxhzdk39wzxhzdk40-logical-time"><a id=Logical_Time></a> Logical Time</h4>
+<h4 id="logical-time"><a id=Logical_Time></a> Logical Time</h4>
 <p>Accumulo 1.2 introduces the concept of logical time. This ensures that timestamps set by accumulo always move forward. This helps avoid problems caused by TabletServers that have different time settings. The per tablet counter gives unique one up time stamps on a per mutation basis. When using time in milliseconds, if two things arrive within the same millisecond then both receive the same timestamp. </p>
 <p>A table can be configured to use logical timestamps at creation time as follows: </p>
 <div class="codehilite"><pre><span class="n">user</span><span class="p">@</span><span class="n">myinstance</span><span class="o">&gt;</span> <span class="n">createtable</span> <span class="o">-</span><span class="n">tl</span> <span class="n">logical</span>
 </pre></div>
 
 
-<h4 id="wzxhzdk41wzxhzdk42-deletes"><a id=Deletes></a> Deletes</h4>
+<h4 id="deletes"><a id=Deletes></a> Deletes</h4>
 <p>Deletes are special keys in accumulo that get sorted along will all the other data. When a delete key is inserted, accumulo will not show anything that has a timestamp less than or equal to the delete key. During major compaction, any keys older than a delete key are omitted from the new file created, and the omitted keys are removed from disk as part of the regular garbage collection process. </p>
-<h3 id="wzxhzdk43wzxhzdk44-filtering-iterators"><a id=Filtering_Iterators></a> Filtering Iterators</h3>
+<h3 id="filtering-iterators"><a id=Filtering_Iterators></a> Filtering Iterators</h3>
 <p>When scanning over a set of key-value pairs it is possible to apply an arbitrary filtering policy through the use of a FilteringIterator. These types of iterators return only key-value pairs that satisfy the filter logic. Accumulo has two built-in filtering iterators that can be configured on any table: AgeOff and RegEx. More can be added by writing a Java class that implements the <br />
 org.apache.accumulo.core.iterators.filter.Filter interface. </p>
 <p>To configure the AgeOff filter to remove data older than a certain date or a fixed amount of time from the present. The following example sets a table to delete everything inserted over 30 seconds ago: </p>
@@ -416,7 +417,7 @@ org.apache.accumulo.core.iterators.filte
 </pre></div>
 
 
-<h2 id="wzxhzdk45wzxhzdk46-aggregating-iterators"><a id=Aggregating_Iterators></a> Aggregating Iterators</h2>
+<h2 id="aggregating-iterators"><a id=Aggregating_Iterators></a> Aggregating Iterators</h2>
 <p>Accumulo allows aggregating iterators to be configured on tables and column families. When an aggregating iterator is set, the iterator is applied across the values associated with any keys that share rowID, column family, and column qualifier. This is similar to the reduce step in MapReduce, which applied some function to all the values associated with a particular key. </p>
 <p>For example, if an aggregating iterator were configured on a table and the following mutations were inserted: </p>
 <div class="codehilite"><pre><span class="n">Row</span>     <span class="n">Family</span> <span class="n">Qualifier</span> <span class="n">Timestamp</span>  <span class="n">Value</span>
@@ -458,7 +459,7 @@ org.apache.accumulo.core.iterators.filte
 <strong>org.apache.accumulo.core.iterators.aggregation.Aggregator</strong> and adding a jar containing that class to Accumulo's lib directory. </p>
 <p>An example of an aggregator can be found under <br />
 accumulo/src/examples/main/java/org/apache/accumulo/examples/aggregation/SortedSetAggregator.java </p>
-<h2 id="wzxhzdk47wzxhzdk48-block-cache"><a id=Block_Cache></a> Block Cache</h2>
+<h2 id="block-cache"><a id=Block_Cache></a> Block Cache</h2>
 <p>In order to increase throughput of commonly accessed entries, Accumulo employs a block cache. This block cache buffers data in memory so that it doesn't have to be read off of disk. The RFile format that Accumulo prefers is a mix of index blocks and data blocks, where the index blocks are used to find the appropriate data blocks. Typical queries to Accumulo result in a binary search over several index blocks followed by a linear scan of one or more data blocks. </p>
 <p>The block cache can be configured on a per-table basis, and all tablets hosted on a tablet server share a single resource pool. To configure the size of the tablet server's block cache, set the following properties: </p>
 <div class="codehilite"><pre><span class="n">tserver</span><span class="p">.</span><span class="n">cache</span><span class="p">.</span><span class="n">data</span><span class="p">.</span><span class="nb">size</span><span class="p">:</span> <span class="n">Specifies</span> <span class="n">the</span> <span class="nb">size</span> <span class="n">of</span> <span class="n">the</span> <span class="n">cache</span> <span class="k">for</span> <span class="n">file</span> <span class="n">data</span> <span class="n">blocks</span><span class="p">.</span>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Table_Design.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Table_Design.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Table_Design.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -223,8 +224,8 @@ Latest 1.5 release: <strong>1.5.3</stron
 <li><a href="Table_Design.html#Document-Partitioned_Indexing">Document-Partitioned Indexing</a></li>
 </ul>
 <hr />
-<h2 id="wzxhzdk10wzxhzdk11-table-design"><a id=Table_Design></a> Table Design</h2>
-<h2 id="wzxhzdk12wzxhzdk13-basic-table"><a id=Basic_Table></a> Basic Table</h2>
+<h2 id="table-design"><a id=Table_Design></a> Table Design</h2>
+<h2 id="basic-table"><a id=Basic_Table></a> Basic Table</h2>
 <p>Since Accumulo tables are sorted by row ID, each table can be thought of as being indexed by the row ID. Lookups performed row ID can be executed quickly, by doing a binary search, first across the tablets, and then within a tablet. Clients should choose a row ID carefully in order to support their desired application. A simple rule is to select a unique identifier as the row ID for each entity to be stored and assign all the other attributes to be tracked to be columns under this row ID. For example, if we have the following data in a comma-separated file: </p>
 <div class="codehilite"><pre>    <span class="n">userid</span><span class="p">,</span><span class="n">age</span><span class="p">,</span><span class="n">address</span><span class="p">,</span><span class="n">account</span><span class="o">-</span><span class="n">balance</span>
 </pre></div>
@@ -251,7 +252,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 </pre></div>
 
 
-<h2 id="wzxhzdk14wzxhzdk15-rowid-design"><a id=RowID_Design></a> RowID Design</h2>
+<h2 id="rowid-design"><a id=RowID_Design></a> RowID Design</h2>
 <p>Often it is necessary to transform the rowID in order to have rows ordered in a way that is optimal for anticipated access patterns. A good example of this is reversing the order of components of internet domain names in order to group rows of the same parent domain together: </p>
 <div class="codehilite"><pre><span class="n">com</span><span class="p">.</span><span class="n">google</span><span class="p">.</span><span class="n">code</span>
 <span class="n">com</span><span class="p">.</span><span class="n">google</span><span class="p">.</span><span class="n">labs</span>
@@ -282,7 +283,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 
 
 <p>Appending dates provides the additional capability of restricting a scan to a given date range. </p>
-<h2 id="wzxhzdk16wzxhzdk17-indexing"><a id=Indexing></a> Indexing</h2>
+<h2 id="indexing"><a id=Indexing></a> Indexing</h2>
 <p>In order to support lookups via more than one attribute of an entity, additional indexes can be built. However, because Accumulo tables can support any number of columns without specifying them beforehand, a single additional index will often suffice for supporting lookups of records in the main table. Here, the index has, as the rowID, the Value or Term from the main table, the column families are the same, and the column qualifier of the index table contains the rowID from the main table. </p>
 <p><img alt="converted table" src="img2.png" /></p>
 <p>Note: We store rowIDs in the column qualifier rather than the Value so that we can have more than one rowID associated with a particular term within the index. If we stored this in the Value we would only see one of the rows in which the value appears since Accumulo is configured by default to return the one most recent value associated with a key. </p>
@@ -313,7 +314,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 
 
 <p>One advantage of the dynamic schema capabilities of Accumulo is that different fields may be indexed into the same physical table. However, it may be necessary to create different index tables if the terms must be formatted differently in order to maintain proper sort order. For example, real numbers must be formatted differently than their usual notation in order to be sorted correctly. In these cases, usually one index per unique data type will suffice. </p>
-<h2 id="wzxhzdk18wzxhzdk19-entity-attribute-and-graph-tables"><a id=Entity-Attribute_and_Graph_Tables></a> Entity-Attribute and Graph Tables</h2>
+<h2 id="entity-attribute-and-graph-tables"><a id=Entity-Attribute_and_Graph_Tables></a> Entity-Attribute and Graph Tables</h2>
 <p>Accumulo is ideal for storing entities and their attributes, especially of the attributes are sparse. It is often useful to join several datasets together on common entities within the same table. This can allow for the representation of graphs, including nodes, their attributes, and connections to other nodes. </p>
 <p>Rather than storing individual events, Entity-Attribute or Graph tables store aggregate information about the entities involved in the events and the relationships between entities. This is often preferrable when single events aren't very useful and when a continuously updated summarization is desired. </p>
 <p>The physical shema for an entity-attribute or graph table is as follows: </p>
@@ -321,7 +322,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 <p>For example, to keep track of employees, managers and products the following entity-attribute table could be used. Note that the weights are not always necessary and are set to 0 when not used. </p>
 <p><img alt="converted table" src="img4.png" />   </p>
 <p>To allow efficient updating of edge weights, an aggregating iterator can be configured to add the value of all mutations applied with the same key. These types of tables can easily be created from raw events by simply extracting the entities, attributes, and relationships from individual events and inserting the keys into Accumulo each with a count of 1. The aggregating iterator will take care of maintaining the edge weights. </p>
-<h2 id="wzxhzdk20wzxhzdk21-document-partitioned-indexing"><a id=Document-Partitioned_Indexing></a> Document-Partitioned Indexing</h2>
+<h2 id="document-partitioned-indexing"><a id=Document-Partitioned_Indexing></a> Document-Partitioned Indexing</h2>
 <p>Using a simple index as described above works well when looking for records that match one of a set of given criteria. When looking for records that match more than one criterion simultaneously, such as when looking for documents that contain all of the words <code>the' and</code>white' and `house', there are several issues. </p>
 <p>First is that the set of all records matching any one of the search terms must be sent to the client, which incurs a lot of network traffic. The second problem is that the client is responsible for performing set intersection on the sets of records returned to eliminate all but the records matching all search terms. The memory of the client may easily be overwhelmed during this operation. </p>
 <p>For these reasons Accumulo includes support for a scheme known as sharded indexing, in which these set operations can be performed at the TabletServers and decisions about which records to include in the result set can be made without incurring network traffic. </p>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Writing_Accumulo_Clients.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Writing_Accumulo_Clients.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/Writing_Accumulo_Clients.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>
@@ -220,7 +221,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 <li><a href="Writing_Accumulo_Clients.html#Reading_Data">Reading Data</a></li>
 </ul>
 <hr />
-<h2 id="wzxhzdk7wzxhzdk8-writing-accumulo-clients"><a id=Writing_Accumulo_Clients></a> Writing Accumulo Clients</h2>
+<h2 id="writing-accumulo-clients"><a id=Writing_Accumulo_Clients></a> Writing Accumulo Clients</h2>
 <p>All clients must first identify the Accumulo instance to which they will be communicating. Code to do this is as follows: </p>
 <div class="codehilite"><pre><span class="n">String</span> <span class="n">instanceName</span> <span class="p">=</span> &quot;<span class="n">myinstance</span>&quot;<span class="p">;</span>
 <span class="n">String</span> <span class="n">zooServers</span> <span class="p">=</span> &quot;<span class="n">zooserver</span><span class="o">-</span><span class="n">one</span><span class="p">,</span><span class="n">zooserver</span><span class="o">-</span><span class="n">two</span>&quot;
@@ -230,7 +231,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 </pre></div>
 
 
-<h2 id="wzxhzdk9wzxhzdk10-writing-data"><a id=Writing_Data></a> Writing Data</h2>
+<h2 id="writing-data"><a id=Writing_Data></a> Writing Data</h2>
 <p>Data are written to Accumulo by creating Mutation objects that represent all the changes to the columns of a single row. The changes are made atomically in the TabletServer. Clients then add Mutations to a BatchWriter which submits them to the appropriate TabletServers. </p>
 <p>Mutations can be created thus: </p>
 <div class="codehilite"><pre><span class="n">Text</span> <span class="n">rowID</span> <span class="p">=</span> <span class="n">new</span> <span class="n">Text</span><span class="p">(</span>&quot;<span class="n">row1</span>&quot;<span class="p">);</span>
@@ -246,7 +247,7 @@ Latest 1.5 release: <strong>1.5.3</stron
 </pre></div>
 
 
-<h3 id="wzxhzdk11wzxhzdk12-batchwriter"><a id=BatchWriter></a> BatchWriter</h3>
+<h3 id="batchwriter"><a id=BatchWriter></a> BatchWriter</h3>
 <p>The BatchWriter is highly optimized to send Mutations to multiple TabletServers and automatically batches Mutations destined for the same TabletServer to amortize network overhead. Care must be taken to avoid changing the contents of any Object passed to the BatchWriter since it keeps objects in memory while batching. </p>
 <p>Mutations are added to a BatchWriter thus: </p>
 <div class="codehilite"><pre><span class="n">long</span> <span class="n">memBuf</span> <span class="p">=</span> 1000000<span class="n">L</span><span class="p">;</span> <span class="o">//</span> <span class="n">bytes</span> <span class="n">to</span> <span class="n">store</span> <span class="n">before</span> <span class="n">sending</span> <span class="n">a</span> <span class="n">batch</span>
@@ -264,9 +265,9 @@ Latest 1.5 release: <strong>1.5.3</stron
 
 <p>An example of using the batch writer can be found at <br />
 accumulo/docs/examples/README.batch </p>
-<h2 id="wzxhzdk13wzxhzdk14-reading-data"><a id=Reading_Data></a> Reading Data</h2>
+<h2 id="reading-data"><a id=Reading_Data></a> Reading Data</h2>
 <p>Accumulo is optimized to quickly retrieve the value associated with a given key, and to efficiently return ranges of consecutive keys and their associated values. </p>
-<h3 id="wzxhzdk15wzxhzdk16-scanner"><a id=Scanner></a> Scanner</h3>
+<h3 id="scanner"><a id=Scanner></a> Scanner</h3>
 <p>To retrieve data, Clients use a Scanner, which provides acts like an Iterator over keys and values. Scanners can be configured to start and stop at particular keys, and to return a subset of the columns available. </p>
 <div class="codehilite"><pre><span class="c1">// specify which visibilities we are allowed to see</span>
 <span class="n">Authorizations</span> <span class="n">auths</span> <span class="o">=</span> <span class="k">new</span> <span class="n">Authorizations</span><span class="p">(</span><span class="s">&quot;public&quot;</span><span class="p">);</span>
@@ -284,7 +285,7 @@ accumulo/docs/examples/README.batch </p>
 </pre></div>
 
 
-<h3 id="wzxhzdk17wzxhzdk18-batchscanner"><a id=BatchScanner></a> BatchScanner</h3>
+<h3 id="batchscanner"><a id=BatchScanner></a> BatchScanner</h3>
 <p>For some types of access, it is more efficient to retrieve several ranges simultaneously. This arises when accessing a set of rows that are not consecutive whose IDs have been retrieved from a secondary index, for example. </p>
 <p>The BatchScanner is configured similarly to the Scanner; it can be configured to retrieve a subset of the columns available, but rather than passing a single Range, BatchScanners accept a set of Ranges. It is important to note that the keys returned by a BatchScanner are not in sorted order since the keys streamed are from multiple TabletServers in parallel. </p>
 <div class="codehilite"><pre><span class="n">ArrayList</span><span class="o">&lt;</span><span class="n">Range</span><span class="o">&gt;</span> <span class="n">ranges</span> <span class="p">=</span> <span class="n">new</span> <span class="n">ArrayList</span><span class="o">&lt;</span><span class="n">Range</span><span class="o">&gt;</span><span class="p">();</span>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/accumulo_user_manual.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/accumulo_user_manual.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/accumulo_user_manual.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/aggregation.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/aggregation.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/aggregation.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/batch.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/batch.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/batch.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/bloom.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/bloom.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/bloom.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/bulkIngest.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/bulkIngest.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/bulkIngest.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/constraints.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/constraints.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/constraints.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>

Modified: websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/dirlist.html
==============================================================================
--- websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/dirlist.html (original)
+++ websites/staging/accumulo/trunk/content/user_manual_1.3-incubating/examples/dirlist.html Wed Jul  1 15:34:48 2015
@@ -141,6 +141,7 @@
       <ul class="dropdown-menu">
 		  <li><a href="/release_notes/1.7.0.html">1.7.0</a></li>
           <li class="divider"></li>
+		  <li><a href="/release_notes/1.6.3.html">1.6.3</a></li>
 		  <li><a href="/release_notes/1.6.2.html">1.6.2</a></li>
 		  <li><a href="/release_notes/1.6.1.html">1.6.1</a></li>
           <li class="divider"></li>



Mime
View raw message