You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by mw...@apache.org on 2018/09/04 19:52:55 UTC
[accumulo-website] branch asf-site updated: Jekyll build from
master:f9dde31
This is an automated email from the ASF dual-hosted git repository.
mwalch pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new b3bf2ee Jekyll build from master:f9dde31
b3bf2ee is described below
commit b3bf2ee70fcc4891651fcd9470bdaa7d2c719ff1
Author: Mike Walch <mw...@apache.org>
AuthorDate: Tue Sep 4 15:52:37 2018 -0400
Jekyll build from master:f9dde31
Removed links to events on contact page (#105)
* Meetup subscription was not renewed and so group no longer exists
* Conference is advertised on main page and through blog posts
so doesn't need to be linked to on 'contact us' page.
---
README.md | 2 +-
blog/2018/03/22/view-metrics-in-grafana.html | 2 +-
contact-us/index.html | 4 ----
contributor/making-release.html | 2 +-
contributors-guide/index.html | 2 +-
docs/2.0/administration/caching.html | 4 ++--
docs/2.0/administration/in-depth-install.html | 2 +-
docs/2.0/administration/kerberos.html | 2 +-
docs/2.0/development/summaries.html | 6 +++---
docs/2.0/getting-started/clients.html | 4 ++--
docs/2.0/getting-started/design.html | 2 +-
docs/2.0/getting-started/table_configuration.html | 2 +-
feed.xml | 12 ++++++------
people/index.html | 5 +++++
redirects.json | 2 +-
release/accumulo-1.9.0/index.html | 4 ++--
release/accumulo-1.9.1/index.html | 2 +-
release/accumulo-2.0.0/index.html | 2 +-
search_data.json | 22 +++++++++++-----------
tour/batch-scanner/index.html | 4 ++--
tour/conditional-writer-code/index.html | 2 +-
21 files changed, 45 insertions(+), 44 deletions(-)
diff --git a/README.md b/README.md
index 3cd5498..e2cd4ce 100644
--- a/README.md
+++ b/README.md
@@ -52,7 +52,7 @@ The source for these tags is at [_plugins/links.rb](_plugins/links.rb).
## Updating property documentation
Building Accumulo generates `properties.md` and `client-properties.md`. To
-regenertate these, do the following.
+regenerate these, do the following.
```
cd <accumulo source dir>
diff --git a/blog/2018/03/22/view-metrics-in-grafana.html b/blog/2018/03/22/view-metrics-in-grafana.html
index 582b575..79c518c 100644
--- a/blog/2018/03/22/view-metrics-in-grafana.html
+++ b/blog/2018/03/22/view-metrics-in-grafana.html
@@ -163,7 +163,7 @@
<li>These graphs only show metrics for the past two hours</li>
</ol>
-<p>The Accumulo monitor could be improved to be better a visualizaiton tool for metrics but this doesn’t make
+<p>The Accumulo monitor could be improved to be better a visualization tool for metrics but this doesn’t make
sense when tools like <a href="http://grafana.org/">Grafana</a>, <a href="https://graphiteapp.org/">Graphite</a>, and <a href="http://ganglia.sourceforge.net/">Ganglia</a> exist and Accumulo can report metrics to these tools
using <a href="/docs/2.0/administration/monitoring-metrics#hadoop-metrics2">Hadoop Metrics2</a>. While it’s easy to configure Accumulo to send metrics, the hard part is
setting up and configuring a metrics visualization tool (i.e Graphite, Ganglia, Grafana/InfluxDB) to collect
diff --git a/contact-us/index.html b/contact-us/index.html
index ead0734..75c270a 100644
--- a/contact-us/index.html
+++ b/contact-us/index.html
@@ -212,10 +212,6 @@ follow discussions as they happen.</p>
<p>Contributions to Apache Accumulo are welcome! If you are interested, read <a href="/how-to-contribute/">how to contribute</a>. If you need help finding something to work on, send a message to our <code class="highlighter-rouge">dev</code> mailing list and we’ll help you find a task that interests you.</p>
-<h2 id="events">Events</h2>
-
-<p>Attend Accumulo events such as <a href="http://accumulosummit.com">Accumulo Summit</a> and meetups hosted by <a href="https://www.meetup.com/Accumulo-Users-DC/">Accumulo Users Group - DC VA MD</a>.</p>
-
</div>
diff --git a/contributor/making-release.html b/contributor/making-release.html
index b27ca5f..3eaa2c9 100644
--- a/contributor/making-release.html
+++ b/contributor/making-release.html
@@ -355,7 +355,7 @@ if this is the latest release of Accumulo.</p>
<ul>
<li>Update the <code class="highlighter-rouge">accumulo.version</code> property in <code class="highlighter-rouge">pom.xml</code> of accumulo-examples</li>
<li>Run <code class="highlighter-rouge">mvn clean verify</code> to confirm that nothing breaks</li>
- <li>Run one of the examples for additinal testing.</li>
+ <li>Run one of the examples for additional testing.</li>
</ul>
<h2 id="references">References</h2>
diff --git a/contributors-guide/index.html b/contributors-guide/index.html
index f604ab9..de75543 100644
--- a/contributors-guide/index.html
+++ b/contributors-guide/index.html
@@ -738,7 +738,7 @@ are the one who knows that this zero-length change in content is correct!</p>
<p>Accumulo primarily uses GitHub (via pull requests) for code reviews, but has access to an instance of <a href="https://reviews.apache.org/">Review Board</a> as well if that is preferred.</p>
-<p>Accumulo operates under the <a href="https://www.apache.org/foundation/glossary#CommitThenReview">Commit-Then-Review</a> (CtR) policy, so a code review does not need to occur prior to commit. However, a commiter has the option to hold a code review before a commit happens if, in their opinion, it would benefit from additional attention. Full details of the code review process for Accumulo is documented <a href="./rb">here</a></p>
+<p>Accumulo operates under the <a href="https://www.apache.org/foundation/glossary#CommitThenReview">Commit-Then-Review</a> (CtR) policy, so a code review does not need to occur prior to commit. However, a committer has the option to hold a code review before a commit happens if, in their opinion, it would benefit from additional attention. Full details of the code review process for Accumulo is documented <a href="./rb">here</a></p>
<h3 id="review-board">Review Board</h3>
diff --git a/docs/2.0/administration/caching.html b/docs/2.0/administration/caching.html
index 5dc73d6..916c155 100644
--- a/docs/2.0/administration/caching.html
+++ b/docs/2.0/administration/caching.html
@@ -364,12 +364,12 @@ for tables where read performance is critical.</p>
</ul>
<p>While the index block cache is enabled by default for all Accumulo tables, users must enable the data block cache by
-settting <a href="/docs/2.0/administration/properties#table_cache_block_enable">table.cache.block.enable</a> to <code class="highlighter-rouge">true</code> in the shell:</p>
+setting <a href="/docs/2.0/administration/properties#table_cache_block_enable">table.cache.block.enable</a> to <code class="highlighter-rouge">true</code> in the shell:</p>
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code>config -t mytable -s table.cache.block.enable=true
</code></pre></div></div>
-<p>Or programatically using <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.9.2/org/apache/accumulo/core/client/admin/TableOperations.html#setProperty-java.lang.String-java.lang.String-java.lang.String-">TableOperations.setProperty()</a>:</p>
+<p>Or programmatically using <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.9.2/org/apache/accumulo/core/client/admin/TableOperations.html#setProperty-java.lang.String-java.lang.String-java.lang.String-">TableOperations.setProperty()</a>:</p>
<div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="n">conn</span><span class="o">.</span><span class="na">tableOperations</span><span class="o">().</span><span class="na">setProperty</span><span class="o">(</span><span class="s">"mytable"</span><span class="o">,</span> <span class="s">"table.cache.block.enable"</span><span class="o">,</span> <span class="s">"true"</span><span class="o">);</span>
</code></pre></div></div>
diff --git a/docs/2.0/administration/in-depth-install.html b/docs/2.0/administration/in-depth-install.html
index aa61937..a5f4573 100644
--- a/docs/2.0/administration/in-depth-install.html
+++ b/docs/2.0/administration/in-depth-install.html
@@ -694,7 +694,7 @@ will expect the KeyStore in the same location.</p>
<h3 id="client-configuration">Client Configuration</h3>
<p>Accumulo clients are configured in a different way than Accumulo servers. Clients are
-configured when <a href="/docs/2.0/getting-started/clients#connecting">an Accumulo Connnector is created</a> using Java builder methods
+configured when <a href="/docs/2.0/getting-started/clients#connecting">an Accumulo Connector is created</a> using Java builder methods
or a <code class="highlighter-rouge">accumulo-client.properties</code> file containing <a href="/docs/2.0/development/client-properties">client properties</a>.</p>
<h3 id="custom-table-tags">Custom Table Tags</h3>
diff --git a/docs/2.0/administration/kerberos.html b/docs/2.0/administration/kerberos.html
index 4c5ae18..0c52880 100644
--- a/docs/2.0/administration/kerberos.html
+++ b/docs/2.0/administration/kerberos.html
@@ -745,7 +745,7 @@ required to set up the SASL transport.</p>
<p>At this point you should have enough configured on the server and client side to interact with
the system. You should verify that the administrative user you chose earlier can successfully
-interact with the sytem.</p>
+interact with the system.</p>
<p>While this example logs in via <code class="highlighter-rouge">kinit</code> with a password, any login method that caches Kerberos tickets
should work.</p>
diff --git a/docs/2.0/development/summaries.html b/docs/2.0/development/summaries.html
index 806b75b..4446264 100644
--- a/docs/2.0/development/summaries.html
+++ b/docs/2.0/development/summaries.html
@@ -465,10 +465,10 @@ Summary Statistics :
</code></pre></div></div>
<p>VisibilitySummarizer has an option <code class="highlighter-rouge">maxCounters</code> that determines the max number
-of column visibilites it will track. Below this option is set and compaction
+of column visibilities it will track. Below this option is set and compaction
is forced to regenerate summary data. The new summary data only has three
-visibilites and now the <code class="highlighter-rouge">tooMany</code> statistic is 4. This is the number of
-visibilites that were not counted.</p>
+visibilities and now the <code class="highlighter-rouge">tooMany</code> statistic is 4. This is the number of
+visibilities that were not counted.</p>
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> root@uno summary_test> config -t summary_test -s table.summarizer.vis.opt.maxCounters=3
root@uno summary_test> compact -w
diff --git a/docs/2.0/getting-started/clients.html b/docs/2.0/getting-started/clients.html
index bc9bc06..69a0843 100644
--- a/docs/2.0/getting-started/clients.html
+++ b/docs/2.0/getting-started/clients.html
@@ -555,10 +555,10 @@ These levels are:</p>
<ol>
<li>The default durability of a table can be set in the Accumulo shell</li>
- <li>When creating a <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.9.2/org/apache/accumulo/core/client/Connector.html">Connector</a>, the default durability can be overriden using <code class="highlighter-rouge">withBatchWriterConfig()</code>
+ <li>When creating a <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.9.2/org/apache/accumulo/core/client/Connector.html">Connector</a>, the default durability can be overridden using <code class="highlighter-rouge">withBatchWriterConfig()</code>
or by setting <a href="/docs/2.0/development/client-properties#batch_writer_durability">batch.writer.durability</a> in <code class="highlighter-rouge">accumulo-client.properties</code>.</li>
<li>
- <p>When a BatchWriter or ConditionalWriter is created, the durability settings above will be overriden
+ <p>When a BatchWriter or ConditionalWriter is created, the durability settings above will be overridden
by the <code class="highlighter-rouge">BatchWriterConfig</code> that is passed in.</p>
<div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="n">BatchWriterConfig</span> <span class="n">cfg</span> <span class="o">=</span> <span class="k">new</span> <span class="n">BatchWriterConfig</span><span class="o">();</span>
diff --git a/docs/2.0/getting-started/design.html b/docs/2.0/getting-started/design.html
index d58eacd..0ecbfff 100644
--- a/docs/2.0/getting-started/design.html
+++ b/docs/2.0/getting-started/design.html
@@ -467,7 +467,7 @@ block is stored in the block cache to speed up future scans.</p>
pairs. The file is written to HDFS by Tablet Servers during a minor compaction. RFiles are
organized using the Index Sequential Access Method (ISAM). RFiles consist of data (key/value) block,
index blocks (which are used to find data block), and meta blocks (which contain
-metadata for bloom filters and summary statistics). Data in an RFile is seperated by
+metadata for bloom filters and summary statistics). Data in an RFile is separated by
locality group. The diagram below shows the logical view and HDFS file view of an RFile.</p>
<p><img src="https://accumulo.apache.org/images/docs/rfile_diagram.png" alt="rfile diagram" />
diff --git a/docs/2.0/getting-started/table_configuration.html b/docs/2.0/getting-started/table_configuration.html
index 472d869..33798ea 100644
--- a/docs/2.0/getting-started/table_configuration.html
+++ b/docs/2.0/getting-started/table_configuration.html
@@ -1004,7 +1004,7 @@ One of the files is a list of files to distcp as shown below.</p>
</code></pre></div></div>
<p>Before the table can be imported, it must be copied using <code class="highlighter-rouge">distcp</code>. After the
-<code class="highlighter-rouge">distcp</code> completea, the cloned table may be deleted.</p>
+<code class="highlighter-rouge">distcp</code> completes, the cloned table may be deleted.</p>
<div class="highlighter-rouge"><div class="highlight"><pre class="highlight"><code> $ hadoop distcp -f /tmp/table1_export/distcp.txt /tmp/table1_export_dest
</code></pre></div></div>
diff --git a/feed.xml b/feed.xml
index 936cb97..841f2a4 100644
--- a/feed.xml
+++ b/feed.xml
@@ -6,8 +6,8 @@
</description>
<link>https://accumulo.apache.org/</link>
<atom:link href="https://accumulo.apache.org/feed.xml" rel="self" type="application/rss+xml"/>
- <pubDate>Thu, 02 Aug 2018 13:39:23 -0400</pubDate>
- <lastBuildDate>Thu, 02 Aug 2018 13:39:23 -0400</lastBuildDate>
+ <pubDate>Tue, 04 Sep 2018 15:52:28 -0400</pubDate>
+ <lastBuildDate>Tue, 04 Sep 2018 15:52:28 -0400</lastBuildDate>
<generator>Jekyll v3.7.3</generator>
@@ -164,7 +164,7 @@ risk from these bugs, which occur during automated recovery from such failures.&
<h2 id="some-wal-recovery-files-were-not-being-properly-cleaned-up">Some WAL recovery files were not being properly cleaned up</h2>
<p>A less serious bug than the above critical bugs was discovered and fixed,
-pertaing to write-ahead log recovery. This bug involved recovery files not
+pertaining to write-ahead log recovery. This bug involved recovery files not
being removed properly when no longer required and was fixed in <a href="https://github.com/apache/accumulo/issues/432">#432</a>.</p>
<h2 id="other-changes">Other Changes</h2>
@@ -198,7 +198,7 @@ successful verification. The integration tests were run against both Hadoop
<item>
<title>Apache Accumulo 1.9.0</title>
<description><p>Apache Accumulo 1.9.0 is a minor release on the 1.x branch. This release would
-be considered a maintainence release on 1.8 branch except there are some API
+be considered a maintenance release on 1.8 branch except there are some API
additions which resulted in a new minor release. Users of 1.8.x versions of
Accumulo should upgrade to 1.9.0. There will be no more bug fix releases on the
1.8 branch. This release contains changes for nearly a hundred issues. See
@@ -228,7 +228,7 @@ works in 2.0.0.</p>
<h3 id="performance-improvements">Performance Improvements</h3>
<p>Accumulo was profiled while running lots of concurrent small scans. During this
-excercise these performance bugs were found and fixed: <a href="https://github.com/apache/accumulo/issues/379">#379</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4778">ACCUMULO-4778</a>,
+exercise these performance bugs were found and fixed: <a href="https://github.com/apache/accumulo/issues/379">#379</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4778">ACCUMULO-4778</a>,
<a href="https://issues.apache.org/jira/browse/ACCUMULO-4779">ACCUMULO-4779</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4781">ACCUMULO-4781</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4782">ACCUMULO-4782</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4788">ACCUMULO-4788</a>,
<a href="https://issues.apache.org/jira/browse/ACCUMULO-4789">ACCUMULO-4789</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4790">ACCUMULO-4790</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4797">ACCUMULO-4797</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4798">ACCUMULO-4798</a>,
<a href="https://issues.apache.org/jira/browse/ACCUMULO-4799">ACCUMULO-4799</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4800">ACCUMULO-4800</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4801">ACCUMULO-4801</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4805">ACCUMULO-4805</a>, and
@@ -459,7 +459,7 @@ on Hadoop 2.2.0, the IT passed with a newer version of Hadoop.</p>
<li>These graphs only show metrics for the past two hours</li>
</ol>
-<p>The Accumulo monitor could be improved to be better a visualizaiton tool for metrics but this doesn’t make
+<p>The Accumulo monitor could be improved to be better a visualization tool for metrics but this doesn’t make
sense when tools like <a href="http://grafana.org/">Grafana</a>, <a href="https://graphiteapp.org/">Graphite</a>, and <a href="http://ganglia.sourceforge.net/">Ganglia</a> exist and Accumulo can report metrics to these tools
using <a href="/docs/2.0/administration/monitoring-metrics#hadoop-metrics2">Hadoop Metrics2</a>. While it’s easy to configure Accumulo to send metrics, the hard part is
setting up and configuring a metrics visualization tool (i.e Graphite, Ganglia, Grafana/InfluxDB) to collect
diff --git a/people/index.html b/people/index.html
index 71760cd..498de11 100644
--- a/people/index.html
+++ b/people/index.html
@@ -441,6 +441,11 @@
<td><a href="http://www.timeanddate.com/time/zones/et">ET</a></td>
</tr>
<tr>
+ <td>Chris McTague</td>
+ <td><a href="http://www.ptech-llc.com">Peterson Technologies</a></td>
+ <td><a href="http://www.timeanddate.com/time/zones/et">ET</a></td>
+ </tr>
+ <tr>
<td>Christian Rohling</td>
<td><a href="http://www.endgame.com">Endgame</a></td>
<td><a href="http://www.timeanddate.com/time/zones/et">ET</a></td>
diff --git a/redirects.json b/redirects.json
index 580f60e..2ec52c0 100644
--- a/redirects.json
+++ b/redirects.json
@@ -1 +1 @@
-{"/release_notes/1.5.1.html":"https://accumulo.apache.org/release/accumulo-1.5.1/","/release_notes/1.6.0.html":"https://accumulo.apache.org/release/accumulo-1.6.0/","/release_notes/1.6.1.html":"https://accumulo.apache.org/release/accumulo-1.6.1/","/release_notes/1.6.2.html":"https://accumulo.apache.org/release/accumulo-1.6.2/","/release_notes/1.7.0.html":"https://accumulo.apache.org/release/accumulo-1.7.0/","/release_notes/1.5.3.html":"https://accumulo.apache.org/release/accumulo-1.5.3/" [...]
\ No newline at end of file
+{"/release_notes/1.5.1.html":"https://accumulo.apache.org/release/accumulo-1.5.1/","/release_notes/1.6.0.html":"https://accumulo.apache.org/release/accumulo-1.6.0/","/release_notes/1.6.1.html":"https://accumulo.apache.org/release/accumulo-1.6.1/","/release_notes/1.6.2.html":"https://accumulo.apache.org/release/accumulo-1.6.2/","/release_notes/1.7.0.html":"https://accumulo.apache.org/release/accumulo-1.7.0/","/release_notes/1.5.3.html":"https://accumulo.apache.org/release/accumulo-1.5.3/" [...]
\ No newline at end of file
diff --git a/release/accumulo-1.9.0/index.html b/release/accumulo-1.9.0/index.html
index 3f4bbd8..2fb141f 100644
--- a/release/accumulo-1.9.0/index.html
+++ b/release/accumulo-1.9.0/index.html
@@ -164,7 +164,7 @@
<p>Apache Accumulo 1.9.0 is a minor release on the 1.x branch. This release would
-be considered a maintainence release on 1.8 branch except there are some API
+be considered a maintenance release on 1.8 branch except there are some API
additions which resulted in a new minor release. Users of 1.8.x versions of
Accumulo should upgrade to 1.9.0. There will be no more bug fix releases on the
1.8 branch. This release contains changes for nearly a hundred issues. See
@@ -194,7 +194,7 @@ works in 2.0.0.</p>
<h3 id="performance-improvements">Performance Improvements</h3>
<p>Accumulo was profiled while running lots of concurrent small scans. During this
-excercise these performance bugs were found and fixed: <a href="https://github.com/apache/accumulo/issues/379">#379</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4778">ACCUMULO-4778</a>,
+exercise these performance bugs were found and fixed: <a href="https://github.com/apache/accumulo/issues/379">#379</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4778">ACCUMULO-4778</a>,
<a href="https://issues.apache.org/jira/browse/ACCUMULO-4779">ACCUMULO-4779</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4781">ACCUMULO-4781</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4782">ACCUMULO-4782</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4788">ACCUMULO-4788</a>,
<a href="https://issues.apache.org/jira/browse/ACCUMULO-4789">ACCUMULO-4789</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4790">ACCUMULO-4790</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4797">ACCUMULO-4797</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4798">ACCUMULO-4798</a>,
<a href="https://issues.apache.org/jira/browse/ACCUMULO-4799">ACCUMULO-4799</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4800">ACCUMULO-4800</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4801">ACCUMULO-4801</a>, <a href="https://issues.apache.org/jira/browse/ACCUMULO-4805">ACCUMULO-4805</a>, and
diff --git a/release/accumulo-1.9.1/index.html b/release/accumulo-1.9.1/index.html
index 8a540fc..4dc4f33 100644
--- a/release/accumulo-1.9.1/index.html
+++ b/release/accumulo-1.9.1/index.html
@@ -195,7 +195,7 @@ risk from these bugs, which occur during automated recovery from such failures.<
<h2 id="some-wal-recovery-files-were-not-being-properly-cleaned-up">Some WAL recovery files were not being properly cleaned up</h2>
<p>A less serious bug than the above critical bugs was discovered and fixed,
-pertaing to write-ahead log recovery. This bug involved recovery files not
+pertaining to write-ahead log recovery. This bug involved recovery files not
being removed properly when no longer required and was fixed in <a href="https://github.com/apache/accumulo/issues/432">#432</a>.</p>
<h2 id="other-changes">Other Changes</h2>
diff --git a/release/accumulo-2.0.0/index.html b/release/accumulo-2.0.0/index.html
index 495bc63..fb99779 100644
--- a/release/accumulo-2.0.0/index.html
+++ b/release/accumulo-2.0.0/index.html
@@ -182,7 +182,7 @@ has been reduced from 20 scripts to the four scripts below:</p>
<ul>
<li><code class="highlighter-rouge">accumulo</code> - mostly left alone except for improved usage</li>
- <li><code class="highlighter-rouge">accumulo-service</code> - manage Accumulo processes as servcies</li>
+ <li><code class="highlighter-rouge">accumulo-service</code> - manage Accumulo processes as services</li>
<li><code class="highlighter-rouge">accumulo-cluster</code> - manage Accumulo on cluster. Replaces <code class="highlighter-rouge">start-all.sh</code> and <code class="highlighter-rouge">stop-all.sh</code></li>
<li><code class="highlighter-rouge">accumulo-util</code> - combines many utility scripts into one script.</li>
</ul>
diff --git a/search_data.json b/search_data.json
index b844660..9ab03e0 100644
--- a/search_data.json
+++ b/search_data.json
@@ -2,7 +2,7 @@
"docs-2-0-administration-caching": {
"title": "Caching",
- "content" : "Accumulo tablet servers have block caches that buffer data in memory to limit reads from disk.This caching has the following benefits: reduces latency when reading data helps alleviate hotspots in tablesEach tablet server has an index and data block cache that is shared by all hosted tablets (see the tablet server diagramto learn more). A typical Accumulo read operation will perform a binary search over several index blocks followed by a linear scanof one or more da [...]
+ "content" : "Accumulo tablet servers have block caches that buffer data in memory to limit reads from disk.This caching has the following benefits: reduces latency when reading data helps alleviate hotspots in tablesEach tablet server has an index and data block cache that is shared by all hosted tablets (see the tablet server diagramto learn more). A typical Accumulo read operation will perform a binary search over several index blocks followed by a linear scanof one or more da [...]
"url": " /docs/2.0/administration/caching",
"categories": "administration"
},
@@ -23,14 +23,14 @@
"docs-2-0-administration-in-depth-install": {
"title": "In-depth Installation",
- "content" : "This document provides detailed instructions for installing Accumulo. For basicinstructions, see the quick installation guide.HardwareBecause we are running essentially two or three systems simultaneously layeredacross the cluster: HDFS, Accumulo and MapReduce, it is typical for hardware toconsist of 4 to 8 cores, and 8 to 32 GB RAM. This is so each running process can haveat least one core and 2 - 4 GB each.One core running HDFS can typically keep 2 to 4 disks busy, [...]
+ "content" : "This document provides detailed instructions for installing Accumulo. For basicinstructions, see the quick installation guide.HardwareBecause we are running essentially two or three systems simultaneously layeredacross the cluster: HDFS, Accumulo and MapReduce, it is typical for hardware toconsist of 4 to 8 cores, and 8 to 32 GB RAM. This is so each running process can haveat least one core and 2 - 4 GB each.One core running HDFS can typically keep 2 to 4 disks busy, [...]
"url": " /docs/2.0/administration/in-depth-install",
"categories": "administration"
},
"docs-2-0-administration-kerberos": {
"title": "Kerberos",
- "content" : "OverviewKerberos is a network authentication protocol that provides a secure way forpeers to prove their identity over an unsecure network in a client-server model.A centralized key-distribution center (KDC) is the service that coordinatesauthentication between a client and a server. Clients and servers use “tickets”,obtained from the KDC via a password or a special file called a “keytab”, tocommunicate with the KDC and prove their identity. A KDC administrator mustcr [...]
+ "content" : "OverviewKerberos is a network authentication protocol that provides a secure way forpeers to prove their identity over an unsecure network in a client-server model.A centralized key-distribution center (KDC) is the service that coordinatesauthentication between a client and a server. Clients and servers use “tickets”,obtained from the KDC via a password or a special file called a “keytab”, tocommunicate with the KDC and prove their identity. A KDC administrator mustcr [...]
"url": " /docs/2.0/administration/kerberos",
"categories": "administration"
},
@@ -149,21 +149,21 @@
"docs-2-0-development-summaries": {
"title": "Summary Statistics",
- "content" : "OverviewAccumulo has the ability to generate summary statistics about data in a tableusing user defined functions. Currently these statistics are only generated fordata written to files. Data recently written to Accumulo that is still inmemory will not contribute to summary statistics.This feature can be used to inform a user about what data is in their table.Summary statistics can also be used by compaction strategies to make decisionsabout which files to compact.S [...]
+ "content" : "OverviewAccumulo has the ability to generate summary statistics about data in a tableusing user defined functions. Currently these statistics are only generated fordata written to files. Data recently written to Accumulo that is still inmemory will not contribute to summary statistics.This feature can be used to inform a user about what data is in their table.Summary statistics can also be used by compaction strategies to make decisionsabout which files to compact.S [...]
"url": " /docs/2.0/development/summaries",
"categories": "development"
},
"docs-2-0-getting-started-clients": {
"title": "Accumulo Clients",
- "content" : "Creating Client CodeIf you are using Maven to create Accumulo client code, add the following to your pom:&lt;dependency&gt; &lt;groupId&gt;org.apache.accumulo&lt;/groupId&gt; &lt;artifactId&gt;accumulo-core&lt;/artifactId&gt; &lt;version&gt;2.0.0&lt;/version&gt;&lt;/dependency&gt;ConnectingBefore writing Accumulo client code, you will need the following information. Accumulo instance name Zookeeper c [...]
+ "content" : "Creating Client CodeIf you are using Maven to create Accumulo client code, add the following to your pom:&lt;dependency&gt; &lt;groupId&gt;org.apache.accumulo&lt;/groupId&gt; &lt;artifactId&gt;accumulo-core&lt;/artifactId&gt; &lt;version&gt;2.0.0&lt;/version&gt;&lt;/dependency&gt;ConnectingBefore writing Accumulo client code, you will need the following information. Accumulo instance name Zookeeper c [...]
"url": " /docs/2.0/getting-started/clients",
"categories": "getting-started"
},
"docs-2-0-getting-started-design": {
"title": "Accumulo Design",
- "content" : "BackgroundThe design of Apache Accumulo is inspired by Google’s BigTable paper.Data ModelAccumulo provides a richer data model than simple key-value stores, but is not afully relational database. Data is represented as key-value pairs, where the key andvalue are comprised of the following elements:All elements of the Key and the Value are represented as byte arrays except forTimestamp, which is a Long. Accumulo sorts keys by element and lexicographicallyin ascending o [...]
+ "content" : "BackgroundThe design of Apache Accumulo is inspired by Google’s BigTable paper.Data ModelAccumulo provides a richer data model than simple key-value stores, but is not afully relational database. Data is represented as key-value pairs, where the key andvalue are comprised of the following elements:All elements of the Key and the Value are represented as byte arrays except forTimestamp, which is a Long. Accumulo sorts keys by element and lexicographicallyin ascending o [...]
"url": " /docs/2.0/getting-started/design",
"categories": "getting-started"
},
@@ -184,7 +184,7 @@
"docs-2-0-getting-started-table-configuration": {
"title": "Table Configuration",
- "content" : "Accumulo tables have a few options that can be configured to alter the defaultbehavior of Accumulo as well as improve performance based on the data stored.These include locality groups, constraints, bloom filters, iterators, and blockcache. See the configuration properties documentation fora complete list of available configuration options.Locality GroupsAccumulo supports storing sets of column families separately on disk to allowclients to efficiently scan over colu [...]
+ "content" : "Accumulo tables have a few options that can be configured to alter the defaultbehavior of Accumulo as well as improve performance based on the data stored.These include locality groups, constraints, bloom filters, iterators, and blockcache. See the configuration properties documentation fora complete list of available configuration options.Locality GroupsAccumulo supports storing sets of column families separately on disk to allowclients to efficiently scan over colu [...]
"url": " /docs/2.0/getting-started/table_configuration",
"categories": "getting-started"
},
@@ -265,7 +265,7 @@
"release-accumulo-1-9-1": {
"title": "Apache Accumulo 1.9.1",
- "content" : "Apache Accumulo 1.9.1 contains bug fixes for a critical data loss bug. Users of1.8.0, 1.8.1, or 1.9.0 are encouraged to upgrade immediately. User Manual - In-depth developer and administrator documentation Javadocs - Accumulo 1.9 API Examples - Code with corresponding readme files that give step bystep instructions for running example codeNotable ChangesFixes for Critical WAL Data Loss Bugs (affects versions 1.8.0-1.9.0)Accumulo 1.9.1 contains multiple bug fixes fo [...]
+ "content" : "Apache Accumulo 1.9.1 contains bug fixes for a critical data loss bug. Users of1.8.0, 1.8.1, or 1.9.0 are encouraged to upgrade immediately. User Manual - In-depth developer and administrator documentation Javadocs - Accumulo 1.9 API Examples - Code with corresponding readme files that give step bystep instructions for running example codeNotable ChangesFixes for Critical WAL Data Loss Bugs (affects versions 1.8.0-1.9.0)Accumulo 1.9.1 contains multiple bug fixes fo [...]
"url": " /release/accumulo-1.9.1/",
"categories": "release"
}
@@ -273,7 +273,7 @@
"release-accumulo-1-9-0": {
"title": "Apache Accumulo 1.9.0",
- "content" : "Apache Accumulo 1.9.0 is a minor release on the 1.x branch. This release wouldbe considered a maintainence release on 1.8 branch except there are some APIadditions which resulted in a new minor release. Users of 1.8.x versions ofAccumulo should upgrade to 1.9.0. There will be no more bug fix releases on the1.8 branch. This release contains changes for nearly a hundred issues. SeeGitHub and JIRA for a list of changes.Below are resources for this release: User Manual - [...]
+ "content" : "Apache Accumulo 1.9.0 is a minor release on the 1.x branch. This release wouldbe considered a maintenance release on 1.8 branch except there are some APIadditions which resulted in a new minor release. Users of 1.8.x versions ofAccumulo should upgrade to 1.9.0. There will be no more bug fix releases on the1.8 branch. This release contains changes for nearly a hundred issues. SeeGitHub and JIRA for a list of changes.Below are resources for this release: User Manual - [...]
"url": " /release/accumulo-1.9.0/",
"categories": "release"
}
@@ -289,7 +289,7 @@
"blog-2018-03-22-view-metrics-in-grafana-html": {
"title": "View Accumulo metrics in Grafana",
- "content" : "The Accumulo monitor provides the easiest way to view Accumulo metrics but it has two limitations: The overview page is limited to 10 graphs These graphs only show metrics for the past two hoursThe Accumulo monitor could be improved to be better a visualizaiton tool for metrics but this doesn’t makesense when tools like Grafana, Graphite, and Ganglia exist and Accumulo can report metrics to these toolsusing Hadoop Metrics2. While it’s easy to configure Accumulo to s [...]
+ "content" : "The Accumulo monitor provides the easiest way to view Accumulo metrics but it has two limitations: The overview page is limited to 10 graphs These graphs only show metrics for the past two hoursThe Accumulo monitor could be improved to be better a visualization tool for metrics but this doesn’t makesense when tools like Grafana, Graphite, and Ganglia exist and Accumulo can report metrics to these toolsusing Hadoop Metrics2. While it’s easy to configure Accumulo to s [...]
"url": " /blog/2018/03/22/view-metrics-in-grafana.html",
"categories": "blog"
}
@@ -313,7 +313,7 @@
"release-accumulo-2-0-0": {
"title": "Apache Accumulo 2.0.0",
- "content" : "Apache Accumulo 2.0.0 is a significant release.Notable ChangesNew API for creating connections to AccumuloA fluent API for clients to build Connector objects was introduced in ACCUMULO-4784.The new API deprecates ClientConfiguration and introduces its own propertiesfile called accumulo-client.properties that ships with the Accumulo tarball.See the client documentation for more information on how to use the new API.Simplified Accumulo scripts and configuration filesAcc [...]
+ "content" : "Apache Accumulo 2.0.0 is a significant release.Notable ChangesNew API for creating connections to AccumuloA fluent API for clients to build Connector objects was introduced in ACCUMULO-4784.The new API deprecates ClientConfiguration and introduces its own propertiesfile called accumulo-client.properties that ships with the Accumulo tarball.See the client documentation for more information on how to use the new API.Simplified Accumulo scripts and configuration filesAcc [...]
"url": " /release/accumulo-2.0.0/",
"categories": "release"
}
diff --git a/tour/batch-scanner/index.html b/tour/batch-scanner/index.html
index b938969..618e1ad 100644
--- a/tour/batch-scanner/index.html
+++ b/tour/batch-scanner/index.html
@@ -180,7 +180,7 @@ will retrieve multiple Ranges of data using multiple threads. A BatchScanner ca
<span class="o">}</span>
</code></pre></div></div>
-<p>We want to calculate the average years of service from a sample of 2000 villians. A BatchScanner would be good for this task because we
+<p>We want to calculate the average years of service from a sample of 2000 villains. A BatchScanner would be good for this task because we
don’t need the returned keys to be sorted. Follow these steps to efficiently scan the table with 10,000 entries.</p>
<ol>
@@ -195,7 +195,7 @@ don’t need the returned keys to be sorted. Follow these steps to efficiently s
and <code class="highlighter-rouge">yearsOfService</code> qualifier.</p>
</li>
<li>
- <p>Finally, use the BatchScanner to calculate the average years of service of 2000 villians.</p>
+ <p>Finally, use the BatchScanner to calculate the average years of service of 2000 villains.</p>
</li>
</ol>
diff --git a/tour/conditional-writer-code/index.html b/tour/conditional-writer-code/index.html
index cabd829..8bd117b 100644
--- a/tour/conditional-writer-code/index.html
+++ b/tour/conditional-writer-code/index.html
@@ -158,7 +158,7 @@
<p class="text-muted">Tour page 11 of 11</p>
</div>
<div id="tour-content">
- <p>Below is a solution to the excercise.</p>
+ <p>Below is a solution to the exercise.</p>
<div class="language-java highlighter-rouge"><div class="highlight"><pre class="highlight"><code> <span class="kd">static</span> <span class="kt">boolean</span> <span class="nf">setAddress</span><span class="o">(</span><span class="n">Connector</span> <span class="n">conn</span><span class="o">,</span> <span class="n">String</span> <span class="n">id</span><span class="o">,</span> <span class="n">String</span> <span class="n">expectedAddr</span><span class="o">,</span> <span class="n">S [...]
<span class="k">try</span> <span class="o">(</span><span class="n">ConditionalWriter</span> <span class="n">writer</span> <span class="o">=</span> <span class="n">conn</span><span class="o">.</span><span class="na">createConditionalWriter</span><span class="o">(</span><span class="s">"GothamPD"</span><span class="o">,</span> <span class="k">new</span> <span class="n">ConditionalWriterConfig</span><span class="o">()))</span> <span class="o">{</span>