This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new c4e031d Automatic Site Publish by Buildbot
c4e031d is described below
commit c4e031d2bace8bbe660608d46397084d88eebfc4
Author: buildbot <[email protected]>
AuthorDate: Mon Nov 23 16:45:54 2020 +0000
Automatic Site Publish by Buildbot
---
output/1.10/examples/sample.html | 2 +-
.../docs/2.x/administration/in-depth-install.html | 6 +++---
output/docs/2.x/configuration/files.html | 6 +++---
output/docs/2.x/configuration/overview.html | 8 ++++----
output/docs/2.x/development/high_speed_ingest.html | 2 +-
output/docs/2.x/development/mapreduce.html | 4 ++--
output/docs/2.x/development/sampling.html | 6 +++---
output/docs/2.x/development/summaries.html | 8 ++++----
output/docs/2.x/security/authentication.html | 4 ++--
output/docs/2.x/security/authorizations.html | 4 ++--
output/docs/2.x/security/on-disk-encryption.html | 4 ++--
output/docs/2.x/security/wire-encryption.html | 2 +-
output/feed.xml | 4 ++--
output/search_data.json | 22 +++++++++++-----------
14 files changed, 41 insertions(+), 41 deletions(-)
diff --git a/output/1.10/examples/sample.html b/output/1.10/examples/sample.html
index b63089b..a608b1a 100644
--- a/output/1.10/examples/sample.html
+++ b/output/1.10/examples/sample.html
@@ -237,7 +237,7 @@ root@instance sampex> scan -t accumulo.metadata -c file
-b 2 -e 2<
<p>Below shows running <code class="language-plaintext
highlighter-rouge">accumulo rfile-info</code> on the file above. This shows the
rfile has a normal default locality group and a sample default locality group.
The output also shows the configuration used to create the sample locality
-group. The sample configuration within a rfile must match the tables sample
+group. The sample configuration within an RFile must match the tables sample
configuration for sample scan to work.</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>$ ./bin/accumulo rfile-info
hdfs://localhost:10000/accumulo/tables/2/default_tablet/A000000s.rf
diff --git a/output/docs/2.x/administration/in-depth-install.html
b/output/docs/2.x/administration/in-depth-install.html
index af1ba98..ad9f5e6 100644
--- a/output/docs/2.x/administration/in-depth-install.html
+++ b/output/docs/2.x/administration/in-depth-install.html
@@ -585,7 +585,7 @@ and specify the following:</p>
</ol>
<p>Accumulo uses <code class="language-plaintext
highlighter-rouge">HADOOP_HOME</code> and <code class="language-plaintext
highlighter-rouge">ZOOKEEPER_HOME</code> to locate Hadoop and Zookeeper jars
-and add them the <code class="language-plaintext
highlighter-rouge">CLASSPATH</code> variable. If you are running a
vendor-specific release of Hadoop
+and add them to the <code class="language-plaintext
highlighter-rouge">CLASSPATH</code> variable. If you are running a
vendor-specific release of Hadoop
or Zookeeper, you may need to change how your <code class="language-plaintext
highlighter-rouge">CLASSPATH</code> is built in <a
href="/docs/2.x/configuration/files#accumulo-envsh">accumulo-env.sh</a>. If
Accumulo has problems later on finding jars, run <code
class="language-plaintext highlighter-rouge">accumulo classpath</code> to print
Accumulo’s
classpath.</p>
@@ -740,7 +740,7 @@ to result in data being leaked to users who should not have
access to that data.
<p>In Hadoop-2.6.0, a new CredentialProvider class was introduced which serves
as a common
implementation to abstract away the storage and retrieval of passwords from
plaintext
storage in configuration files. Any Property marked with the <code
class="language-plaintext highlighter-rouge">Sensitive</code> annotation
-is a candidate for use with these CredentialProviders. For version of Hadoop
which lack
+is a candidate for use with these CredentialProviders. For versions of Hadoop
which lack
these classes, the feature will just be unavailable for use.</p>
<p>A comma separated list of CredentialProviders can be configured using the
Accumulo Property
@@ -767,7 +767,7 @@ Each entry in the KeyStore is the Accumulo Property key
name. For example, to st
</code></pre></div></div>
<p>This configuration will then transparently extract the <a
href="/docs/2.x/configuration/server-properties#instance_secret">instance.secret</a>
from
-the configured KeyStore and alleviates a human readable storage of the
sensitive
+the configured KeyStore and eliminates human readable storage of the sensitive
property.</p>
<p>A KeyStore can also be stored in HDFS, which will make the KeyStore readily
available to
diff --git a/output/docs/2.x/configuration/files.html
b/output/docs/2.x/configuration/files.html
index a05435b..4291e8f 100644
--- a/output/docs/2.x/configuration/files.html
+++ b/output/docs/2.x/configuration/files.html
@@ -450,7 +450,7 @@ in Java using the following code:</p>
<h2 id="accumulo-envsh">accumulo-env.sh</h2>
<p>The <a
href="https://github.com/apache/accumulo/blob/main/assemble/conf/accumulo-env.sh";>accumulo-env.sh</a>
file configures the Java classpath and JVM options needed to run
-Accumulo processes. See the [quick install] for help with configuring this
file.</p>
+Accumulo processes. See the <a
href="/docs/2.x/getting-started/quickstart#configuring-accumulo">quick
start</a> for help with configuring this file.</p>
<h2 id="log-configuration-files">Log configuration files</h2>
@@ -471,7 +471,7 @@ Accumulo processes. See the [quick install] for help with
configuring this file.
<h2 id="host-files">Host files</h2>
<p>The <code class="language-plaintext
highlighter-rouge">accumulo-cluster</code> script uses the host files below to
determine where Accumulo processes should be run.
-These files are not in <code class="language-plaintext
highlighter-rouge">conf/</code> directory the Accumulo release tarball by
default. They can be created by running
+These files are not in the <code class="language-plaintext
highlighter-rouge">conf/</code> directory of the Accumulo release tarball by
default. They can be created by running
the command <code class="language-plaintext
highlighter-rouge">accumulo-cluster create-config</code>.</p>
<h3 id="gc">gc</h3>
@@ -481,7 +481,7 @@ to run standby Garbage Collectors that can take over if the
lead Garbage Collect
<h3 id="masters">masters</h3>
-<p>Contains a list of hosts where <a
href="/docs/2.x/getting-started/design#master">Master</a> processes should run.
While only one host needed, others can be specified
+<p>Contains a list of hosts where <a
href="/docs/2.x/getting-started/design#master">Master</a> processes should run.
While only one host is needed, others can be specified
to run on standby Masters that can take over if the lead Master fails.</p>
<h3 id="monitor">monitor</h3>
diff --git a/output/docs/2.x/configuration/overview.html
b/output/docs/2.x/configuration/overview.html
index 56b25a3..cfbb2d5 100644
--- a/output/docs/2.x/configuration/overview.html
+++ b/output/docs/2.x/configuration/overview.html
@@ -432,7 +432,7 @@
<h2 id="server-configuration">Server Configuration</h2>
<p>Accumulo processes (i.e master, tablet server, monitor, etc) are configured
by <a href="/docs/2.x/configuration/server-properties">server properties</a>
whose values can be
-set in the following configuration locations (with increasing precedence) that
are described in detail below:</p>
+set in the following configuration locations (with increasing precedence):</p>
<ol>
<li><a href="#default">Default</a> - All properties have a default value</li>
@@ -465,7 +465,7 @@ in their description. Setting properties in
accumulo.properties allows you to co
<h3 id="system">System</h3>
-<p>System configuration refers to <a
href="/docs/2.x/configuration/server-properties">server properties</a> set for
the entire Accumulo instance/cluster. These settings are stored in ZooKeeper
and can identified by <strong>zk mutable: yes</strong>
+<p>System configuration refers to <a
href="/docs/2.x/configuration/server-properties">server properties</a> set for
the entire Accumulo instance/cluster. These settings are stored in ZooKeeper
and can be identified by <strong>zk mutable: yes</strong>
in their description on the <a
href="/docs/2.x/configuration/server-properties">server properties</a> page.
System configuration will override any site configuration set in <a
href="/docs/2.x/configuration/files#accumuloproperties">accumulo.properties</a>.
While most system configuration
settings take effect immediately, some require a restart of the process which
is indicated in the <strong>zk mutable</strong> section of their description.
System configuration can be set using
the following shell command:</p>
@@ -522,8 +522,8 @@ into these warnings should be reconsidered.</p>
<li><code class="language-plaintext highlighter-rouge">config -t
<TABLE></code> - view configuration for a specific table</li>
</ul>
-<p>Below is example shell output from viewing configuration for the table
<code class="language-plaintext highlighter-rouge">foo</code>. Please note how
<code class="language-plaintext
highlighter-rouge">table.compaction.major.ratio</code>
-is set in multiple locations but the value <code class="language-plaintext
highlighter-rouge">1.6</code> set in the <code class="language-plaintext
highlighter-rouge">table</code> scope is used as it has the highest
precedence.</p>
+<p>Below is an example shell output from viewing configuration for the table
<code class="language-plaintext highlighter-rouge">foo</code>. Please note how
<code class="language-plaintext
highlighter-rouge">table.compaction.major.ratio</code>
+is set in multiple locations, but the value <code class="language-plaintext
highlighter-rouge">1.6</code> set in the <code class="language-plaintext
highlighter-rouge">table</code> scope is used because it has the highest
precedence.</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>root@accumulo-instance> config -t foo
---------+---------------------------------------------+-----------------------
diff --git a/output/docs/2.x/development/high_speed_ingest.html
b/output/docs/2.x/development/high_speed_ingest.html
index b563ed7..c06ff56 100644
--- a/output/docs/2.x/development/high_speed_ingest.html
+++ b/output/docs/2.x/development/high_speed_ingest.html
@@ -444,7 +444,7 @@ hardware. Tables can be split at any time by using the
shell:</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>user@myinstance mytable> addsplits -sf
/local_splitfile -t mytable
</code></pre></div></div>
-<p>For the purposes of providing parallelism to ingest it is not necessary to
create more
+<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
diff --git a/output/docs/2.x/development/mapreduce.html
b/output/docs/2.x/development/mapreduce.html
index b3c6668..f089961 100644
--- a/output/docs/2.x/development/mapreduce.html
+++ b/output/docs/2.x/development/mapreduce.html
@@ -467,7 +467,7 @@ MapReduce jobs to run with both Accumulo’s & Hadoop’s
dependencies on th
<p>Since 2.0, Accumulo no longer has the same versions for dependencies as
Hadoop. While this allows
Accumulo to update its dependencies more frequently, it can cause problems if
both Accumulo’s &
Hadoop’s dependencies are on the classpath of the MapReduce job. When
launching a MapReduce job that
-use Accumulo, you should build a <a
href="https://maven.apache.org/plugins/maven-shade-plugin/index.html";>shaded
jar</a> with all of your dependencies and complete the following
+uses Accumulo, you should build a <a
href="https://maven.apache.org/plugins/maven-shade-plugin/index.html";>shaded
jar</a> with all of your dependencies and complete the following
steps so YARN only includes Hadoop code (and not all of Hadoop’s dependencies)
when running your MapReduce job:</p>
<ol>
@@ -578,7 +578,7 @@ your job with <code class="language-plaintext
highlighter-rouge">yarn</code> com
<h2 id="write-output-to-rfiles-in-hdfs">Write output to RFiles in HDFS</h2>
-<p>Follow the step below to have a MapReduce job output to RFiles in HDFS.
These files
+<p>Follow the steps below to have a MapReduce job output to RFiles in HDFS.
These files
can then be bulk imported into Accumulo:</p>
<ol>
diff --git a/output/docs/2.x/development/sampling.html
b/output/docs/2.x/development/sampling.html
index 9cc554a..63ce4ba 100644
--- a/output/docs/2.x/development/sampling.html
+++ b/output/docs/2.x/development/sampling.html
@@ -429,7 +429,7 @@ This sample data is kept up to date as a table is mutated.
What key values are
placed in the sample data is configurable per table.</p>
<p>This feature can be used for query estimation and optimization. For an
example
-of estimation assume an Accumulo table is configured to generate a sample
+of estimation, assume an Accumulo table is configured to generate a sample
containing one millionth of a tables data. If a query is executed against the
sample and returns one thousand results, then the same query against all the
data would probably return a billion results. A nice property of having
@@ -452,11 +452,11 @@ for examples of how to configure a <a
href="https://static.javadoc.io/org.apache
<p>Once a table is configured with a <a
href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/2.0.0/org/apache/accumulo/core/client/sample/Sampler.html";>Sampler</a>,
all writes after that point will
generate sample data. For data written before sampling was configured, sample
data will not be present. A compaction can be initiated that only compacts the
-files in the table that do not have sample data. The <a
href="https://github.com/apache/accumulo-examples/blob/main/docs/sample.md";>sampling
example</a>
+files in the table that do not have sample data. The <a
href="https://github.com/apache/accumulo-examples/blob/main/docs/sample.md";>sampling
example</a>
shows how to do this.</p>
<p>If the sampling configuration of a table is changed, then Accumulo will
start
-generating new sample data with the new configuration. However old data will
+generating new sample data with the new configuration. However, old data will
still have sample data generated with the previous configuration. A selective
compaction can also be issued in this case to regenerate the sample data.</p>
diff --git a/output/docs/2.x/development/summaries.html
b/output/docs/2.x/development/summaries.html
index 94da5df..6da5c08 100644
--- a/output/docs/2.x/development/summaries.html
+++ b/output/docs/2.x/development/summaries.html
@@ -435,7 +435,7 @@ about which files to compact.</p>
<p>Summary data is stored in each file Accumulo produces. Accumulo can gather
summary information from across a cluster merging it along the way. In order
-for this to be fast the, summary information should fit in cache. There is a
+for this to be fast, the summary information should fit in cache. There is a
dedicated cache for summary data on each tserver with a configurable size. In
order for summary data to fit in cache, it should probably be small.</p>
@@ -454,7 +454,7 @@ ranges per a file. However, the ranges are not granular
enough to completely
offset extra data.</p>
<p>Any source of inaccuracies is reported when summary information is
requested.
-In the shell examples below this can be seen on the <code
class="language-plaintext highlighter-rouge">File Statistics</code> line.
+In the shell examples below, this can be seen on the <code
class="language-plaintext highlighter-rouge">File Statistics</code> line.
For files missing summary information, the compact command in the shell has a
<code class="language-plaintext highlighter-rouge">--sf-no-summary</code>
option. This options compacts files that do not have the
summary information configured for the table. The compact command also has the
@@ -477,7 +477,7 @@ information.</p>
<h2 id="permissions">Permissions</h2>
<p>Because summary data may be derived from sensitive data, requesting summary
data
-requires a special permission. User must have the table permission
+requires a special permission. Users must have the table permission
<code class="language-plaintext highlighter-rouge">GET_SUMMARIES</code> in
order to retrieve summary data.</p>
<h2 id="bulk-import">Bulk import</h2>
@@ -489,7 +489,7 @@ class has options for creating RFiles with embedded summary
data.</p>
<h2 id="examples">Examples</h2>
-<p>This example walks through using summarizers in the Accumulo shell. Below a
+<p>This example walks through using summarizers in the Accumulo shell. Below,
a
table is created and some data is inserted to summarize.</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>root@uno> createtable summary_test
diff --git a/output/docs/2.x/security/authentication.html
b/output/docs/2.x/security/authentication.html
index 95630f2..07da6dd 100644
--- a/output/docs/2.x/security/authentication.html
+++ b/output/docs/2.x/security/authentication.html
@@ -471,7 +471,7 @@ Please confirm new password for 'bob': ****
<h2 id="authenticating-users">Authenticating users</h2>
<p>Users are authenticated when they <a
href="/docs/2.x/getting-started/clients#creating-an-accumulo-client">create an
Accumulo client</a>
-or when the log in to the <a href="/docs/2.x/getting-started/shell">Accumulo
shell</a>.</p>
+or when they log in to the <a href="/docs/2.x/getting-started/shell">Accumulo
shell</a>.</p>
<p>Authentication can also be tested in the shell:</p>
@@ -487,7 +487,7 @@ Valid
<h2 id="changing-user-passwords">Changing user passwords</h2>
-<p>A user’s password can changed be in the shell:</p>
+<p>A user’s password can be changed in the shell:</p>
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre
class="highlight"><code>root@uno> passwd -u bob
Enter current password for 'root': ******
diff --git a/output/docs/2.x/security/authorizations.html
b/output/docs/2.x/security/authorizations.html
index f3f7924..984477f 100644
--- a/output/docs/2.x/security/authorizations.html
+++ b/output/docs/2.x/security/authorizations.html
@@ -514,7 +514,7 @@ the <a href="/docs/2.x/getting-started/shell">Accumulo
shell</a>, use the <code
retrieved and modified in Java using <code class="language-plaintext
highlighter-rouge">getUserAuthorizations</code> and <code
class="language-plaintext highlighter-rouge">changeUserAuthorizations</code>
methods of <a
href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/2.0.0/org/apache/accumulo/core/client/admin/SecurityOperations.html";>SecurityOperations</a>.</p>
-<p>When a user creates a <a
href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/2.0.0/org/apache/accumulo/core/client/Scanner.html";>Scanner</a>
or <a
href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/2.0.0/org/apache/accumulo/core/client/BatchScanner.html";>BatchScanner</a>
a set of <a
href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/2.0.0/org/apache/accumulo/core/security/Authorizations.html";>Authorizations</a>
is passed.
+<p>When a user creates a <a
href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/2.0.0/org/apache/accumulo/core/client/Scanner.html";>Scanner</a>
or <a
href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/2.0.0/org/apache/accumulo/core/client/BatchScanner.html";>BatchScanner</a>,
a set of <a
href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/2.0.0/org/apache/accumulo/core/security/Authorizations.html";>Authorizations</a>
is passed.
If the Authorizations passed to the scanner are not a subset of the user’s
Authorizations,
then an exception will be thrown.</p>
@@ -535,7 +535,7 @@ disable the bulk import permission.</p>
<p>For applications serving many users, it is not expected that an Accumulo
user
will be created for each application user. In this case an Accumulo user with
-all authorizations needed by any of the applications users must be created. To
+all authorizations needed by any of the application’s users must be created. To
service queries, the application should create a scanner with the application
user’s authorizations. These authorizations could be obtained from a trusted
3rd
party.</p>
diff --git a/output/docs/2.x/security/on-disk-encryption.html
b/output/docs/2.x/security/on-disk-encryption.html
index 13efb40..eb8bdcf 100644
--- a/output/docs/2.x/security/on-disk-encryption.html
+++ b/output/docs/2.x/security/on-disk-encryption.html
@@ -472,7 +472,7 @@ required to perform decryption. The FileDecrypter only has
one method:</p>
<h2 id="things-to-keep-in-mind">Things to keep in mind</h2>
<p>The on disk encryption configured here is only for RFiles and Write Ahead
Logs (WALs). The majority of data in Accumulo
-is written to disk with these files but there are a few scenarios that can
take place where data will be unencrypted,
+is written to disk with these files, but there are a few scenarios that can
take place where data will be unencrypted,
even with the crypto service enabled.</p>
<h3 id="sorted-wals">Sorted WALs</h3>
@@ -485,7 +485,7 @@ is finished, these unencrypted files will be removed.</p>
<p>For queries, data is decrypted when read from RFiles and cached in memory.
This means that data is unencrypted in memory
while Accumulo is running. Depending on the situation, this also means that
some data can be printed to logs. A stacktrace being logged
-during an exception is one example. Accumulo developers have made sure not to
expose data protected by authorizations during logging but
+during an exception is one example. Accumulo developers have made sure not to
expose data protected by authorizations during logging, but
its the additional data that gets encrypted on disk that could be exposed in a
log file.</p>
<h3 id="bulk-import">Bulk Import</h3>
diff --git a/output/docs/2.x/security/wire-encryption.html
b/output/docs/2.x/security/wire-encryption.html
index a6e54bc..2d0cca8 100644
--- a/output/docs/2.x/security/wire-encryption.html
+++ b/output/docs/2.x/security/wire-encryption.html
@@ -460,7 +460,7 @@ these files already exist.</p>
<p>Optionally, SSL client-authentication (two-way SSL) can also be enabled by
setting
<a
href="/docs/2.x/configuration/server-properties#instance_rpc_ssl_clientAuth">instance.rpc.ssl.clientAuth</a>
<code class="language-plaintext highlighter-rouge">true</code> in <code
class="language-plaintext highlighter-rouge">accumulo.properties</code>.
-This requires that each client has access to valid certificate to set up a
secure connection
+This requires that each client has access to a valid certificate to set up a
secure connection
to the servers. By default, Accumulo uses one-way SSL which does not require
clients to have
their own certificate.</p>
diff --git a/output/feed.xml b/output/feed.xml
index 2fe1ca0..c5fb7fb 100644
--- a/output/feed.xml
+++ b/output/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, 12 Nov 2020 16:34:35 +0000</pubDate>
- <lastBuildDate>Thu, 12 Nov 2020 16:34:35 +0000</lastBuildDate>
+ <pubDate>Mon, 23 Nov 2020 16:45:48 +0000</pubDate>
+ <lastBuildDate>Mon, 23 Nov 2020 16:45:48 +0000</lastBuildDate>
<generator>Jekyll v4.1.1</generator>
diff --git a/output/search_data.json b/output/search_data.json
index 04dd2fd..3031c7c 100644
--- a/output/search_data.json
+++ b/output/search_data.json
@@ -23,7 +23,7 @@
"docs-2-x-administration-in-depth-install": {
"title": "In-depth Installation",
- "content" : "This document provides detailed instructions for
installing Accumulo. For basicinstructions, see the quick start.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, so each machi [...]
+ "content" : "This document provides detailed instructions for
installing Accumulo. For basicinstructions, see the quick start.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, so each machi [...]
"url": " /docs/2.x/administration/in-depth-install",
"categories": "administration"
},
@@ -72,14 +72,14 @@
"docs-2-x-configuration-files": {
"title": "Configuration Files",
- "content" : "Accumulo has the following configuration files
which can be found in theconf/ directory of the Accumulo release
tarball.accumulo.propertiesThe accumulo.properties file configures Accumulo
server processes usingserver properties. This file can be found in the
conf/direcory. It is needed on every host that runs Accumulo processes.
Therfore, any configuration should bereplicated to all hosts of the Accumulo
cluster. If a property is not configured here, it might have bee [...]
+ "content" : "Accumulo has the following configuration files
which can be found in theconf/ directory of the Accumulo release
tarball.accumulo.propertiesThe accumulo.properties file configures Accumulo
server processes usingserver properties. This file can be found in the
conf/direcory. It is needed on every host that runs Accumulo processes.
Therfore, any configuration should bereplicated to all hosts of the Accumulo
cluster. If a property is not configured here, it might have bee [...]
"url": " /docs/2.x/configuration/files",
"categories": "configuration"
},
"docs-2-x-configuration-overview": {
"title": "Configuration Overview",
- "content" : "Configuration is managed differently for Accumulo
clients and servers.Client ConfigurationAccumulo clients are created using Java
builder methods, a Java properties object or anaccumulo-client.properties file
containing client properties.Server ConfigurationAccumulo processes (i.e
master, tablet server, monitor, etc) are configured by server properties whose
values can beset in the following configuration locations (with increasing
precedence) that are described in de [...]
+ "content" : "Configuration is managed differently for Accumulo
clients and servers.Client ConfigurationAccumulo clients are created using Java
builder methods, a Java properties object or anaccumulo-client.properties file
containing client properties.Server ConfigurationAccumulo processes (i.e
master, tablet server, monitor, etc) are configured by server properties whose
values can beset in the following configuration locations (with increasing
precedence): Default - All properti [...]
"url": " /docs/2.x/configuration/overview",
"categories": "configuration"
},
@@ -100,7 +100,7 @@
"docs-2-x-development-high-speed-ingest": {
"title": "High-Speed Ingest",
- "content" : "Accumulo is often used as part of a larger data
processing and storage system. Tomaximize the performance of a parallel system
involving Accumulo, the ingestionand query components should be designed to
provide enough parallelism andconcurrency to avoid creating bottlenecks for
users and other systems writing toand reading from Accumulo. There are several
ways to achieve high ingestperformance.Pre-Splitting New TablesNew tables
consist of a single tablet by default. A [...]
+ "content" : "Accumulo is often used as part of a larger data
processing and storage system. Tomaximize the performance of a parallel system
involving Accumulo, the ingestionand query components should be designed to
provide enough parallelism andconcurrency to avoid creating bottlenecks for
users and other systems writing toand reading from Accumulo. There are several
ways to achieve high ingestperformance.Pre-Splitting New TablesNew tables
consist of a single tablet by default. A [...]
"url": " /docs/2.x/development/high_speed_ingest",
"categories": "development"
},
@@ -114,7 +114,7 @@
"docs-2-x-development-mapreduce": {
"title": "MapReduce",
- "content" : "Accumulo tables can be used as the source and
destination of MapReduce jobs.General MapReduce configurationAdd Accumulo’s
MapReduce API to your dependenciesIf you are using Maven, add the following
dependency to your pom.xml to use Accumulo’s MapReduce
API:&lt;dependency&gt;
&lt;groupId&gt;org.apache.accumulo&lt;/groupId&gt;
&lt;artifactId&gt;accumulo-hadoop-mapreduce&lt;/artifactId&gt;
&lt;version&gt;2.0.0&lt;/ve [...]
+ "content" : "Accumulo tables can be used as the source and
destination of MapReduce jobs.General MapReduce configurationAdd Accumulo’s
MapReduce API to your dependenciesIf you are using Maven, add the following
dependency to your pom.xml to use Accumulo’s MapReduce
API:&lt;dependency&gt;
&lt;groupId&gt;org.apache.accumulo&lt;/groupId&gt;
&lt;artifactId&gt;accumulo-hadoop-mapreduce&lt;/artifactId&gt;
&lt;version&gt;2.0.0&lt;/ve [...]
"url": " /docs/2.x/development/mapreduce",
"categories": "development"
},
@@ -128,7 +128,7 @@
"docs-2-x-development-sampling": {
"title": "Sampling",
- "content" : "OverviewAccumulo has the ability to generate and
scan a per table set of sample data.This sample data is kept up to date as a
table is mutated. What key values areplaced in the sample data is configurable
per table.This feature can be used for query estimation and optimization. For
an exampleof estimation assume an Accumulo table is configured to generate a
samplecontaining one millionth of a tables data. If a query is executed
against thesample and returns one th [...]
+ "content" : "OverviewAccumulo has the ability to generate and
scan a per table set of sample data.This sample data is kept up to date as a
table is mutated. What key values areplaced in the sample data is configurable
per table.This feature can be used for query estimation and optimization. For
an exampleof estimation, assume an Accumulo table is configured to generate a
samplecontaining one millionth of a tables data. If a query is executed
against thesample and returns one t [...]
"url": " /docs/2.x/development/sampling",
"categories": "development"
},
@@ -142,7 +142,7 @@
"docs-2-x-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.x/development/summaries",
"categories": "development"
},
@@ -212,14 +212,14 @@
"docs-2-x-security-authentication": {
"title": "Authentication",
- "content" : "Accumulo has authentication to verify the identity
of users.ConfigurationAccumulo can be configured to use different
authentication methods: Method Setting for
instance.security.authenticator Password (default)
org.apache.accumulo.server.security.handler.ZKAuthenticator
Kerberos org.apache.accumulo.server.security.handler.KerberosAuthenticator
All authentication methods implement Authenticator. The default ( [...]
+ "content" : "Accumulo has authentication to verify the identity
of users.ConfigurationAccumulo can be configured to use different
authentication methods: Method Setting for
instance.security.authenticator Password (default)
org.apache.accumulo.server.security.handler.ZKAuthenticator
Kerberos org.apache.accumulo.server.security.handler.KerberosAuthenticator
All authentication methods implement Authenticator. The default ( [...]
"url": " /docs/2.x/security/authentication",
"categories": "security"
},
"docs-2-x-security-authorizations": {
"title": "Authorizations",
- "content" : "In Accumulo, data is written with security labels
that limit access to only users with the
properauthorizations.ConfigurationAccumulo’s Authorizor is configured by
setting instance.security.authorizor. The defaultauthorizor is the ZKAuthorizor
which is describedbelow.Security LabelsEvery Key-Value pair in Accumulo has its
own security label, stored under the column visibilityelement of the key, which
is used to determine whether a given user meets the securityrequirem [...]
+ "content" : "In Accumulo, data is written with security labels
that limit access to only users with the
properauthorizations.ConfigurationAccumulo’s Authorizor is configured by
setting instance.security.authorizor. The defaultauthorizor is the ZKAuthorizor
which is describedbelow.Security LabelsEvery Key-Value pair in Accumulo has its
own security label, stored under the column visibilityelement of the key, which
is used to determine whether a given user meets the securityrequirem [...]
"url": " /docs/2.x/security/authorizations",
"categories": "security"
},
@@ -233,7 +233,7 @@
"docs-2-x-security-on-disk-encryption": {
"title": "On Disk Encryption",
- "content" : "For an additional layer of security, Accumulo can
encrypt files stored on disk. On Disk encryption was reworked for 2.0, making
it easier to configure and more secure. The files that can be encrypted
include: RFiles and Write Ahead Logs (WALs). NOTE: This feature is considered
experimental. For more information, see the notes below.ConfigurationTo encrypt
all tables on disk, encryption must be enabled before an Accumulo instance is
initialized. If on disk encryptio [...]
+ "content" : "For an additional layer of security, Accumulo can
encrypt files stored on disk. On Disk encryption was reworked for 2.0, making
it easier to configure and more secure. The files that can be encrypted
include: RFiles and Write Ahead Logs (WALs). NOTE: This feature is considered
experimental. For more information, see the notes below.ConfigurationTo encrypt
all tables on disk, encryption must be enabled before an Accumulo instance is
initialized. If on disk encryptio [...]
"url": " /docs/2.x/security/on-disk-encryption",
"categories": "security"
},
@@ -254,7 +254,7 @@
"docs-2-x-security-wire-encryption": {
"title": "Wire Encryption",
- "content" : "Accumulo, through Thrift’s TSSLTransport, provides
the ability to encryptwire communication between Accumulo servers and clients
using securesockets layer (SSL). SSL certificates signed by the same
certificate authoritycontrol the “circle of trust” in which a secure connection
can be established.Typically, each host running Accumulo processes would be
given a certificatewhich identifies itself.Clients can optionally also be given
a certificate, when client-auth is ena [...]
+ "content" : "Accumulo, through Thrift’s TSSLTransport, provides
the ability to encryptwire communication between Accumulo servers and clients
using securesockets layer (SSL). SSL certificates signed by the same
certificate authoritycontrol the “circle of trust” in which a secure connection
can be established.Typically, each host running Accumulo processes would be
given a certificatewhich identifies itself.Clients can optionally also be given
a certificate, when client-auth is ena [...]
"url": " /docs/2.x/security/wire-encryption",
"categories": "security"
},
