Jekyll build from master:29778dd Added more links between pages and javadocs
Project: http://git-wip-us.apache.org/repos/asf/accumulo-website/repo Commit: http://git-wip-us.apache.org/repos/asf/accumulo-website/commit/2c7f1e8c Tree: http://git-wip-us.apache.org/repos/asf/accumulo-website/tree/2c7f1e8c Diff: http://git-wip-us.apache.org/repos/asf/accumulo-website/diff/2c7f1e8c Branch: refs/heads/asf-site Commit: 2c7f1e8cda3fc7d4412554db3d1e53f8bf3d292f Parents: a3b6413 Author: Mike Walch <[email protected]> Authored: Thu May 25 10:21:20 2017 -0400 Committer: Mike Walch <[email protected]> Committed: Thu May 25 10:21:20 2017 -0400 ---------------------------------------------------------------------- docs/unreleased/getting-started/clients.html | 4 +- docs/unreleased/getting-started/design.html | 18 ++++----- .../getting-started/table_configuration.html | 41 +++++++++----------- feed.xml | 4 +- 4 files changed, 32 insertions(+), 35 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/2c7f1e8c/docs/unreleased/getting-started/clients.html ---------------------------------------------------------------------- diff --git a/docs/unreleased/getting-started/clients.html b/docs/unreleased/getting-started/clients.html index 35c2a6c..baa52a8 100644 --- a/docs/unreleased/getting-started/clients.html +++ b/docs/unreleased/getting-started/clients.html @@ -513,7 +513,7 @@ to efficiently return ranges of consecutive keys and their associated values.</p <h3 id="scanner">Scanner</h3> -<p>To retrieve data, Clients use a <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1org/apache/accumulo/core/client/Scanner.html";>Scanner</a>, which acts like an Iterator over +<p>To retrieve data, Clients use a <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/Scanner.html";>Scanner</a>, which 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> @@ -565,7 +565,7 @@ for example code that uses the IsolatedScanner.</p> 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 <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/BatchScanner.html";>BatchScanner</a> is configured similarly to the <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1org/apache/accumulo/core/client/Scanner.html";>Scanner</a>; it can be configured to +<p>The <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/BatchScanner.html";>BatchScanner</a> is configured similarly to the <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/Scanner.html";>Scanner</a>; it can be configured to retrieve a subset of the columns available, but rather than passing a single <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/data/Range.html";>Range</a>, BatchScanners accept a set of Ranges. It is important to note that the keys returned by a <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/BatchScanner.html";>BatchScanner</a> are not in sorted order since the keys streamed are from multiple http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/2c7f1e8c/docs/unreleased/getting-started/design.html ---------------------------------------------------------------------- diff --git a/docs/unreleased/getting-started/design.html b/docs/unreleased/getting-started/design.html index e803da1..47067b4 100644 --- a/docs/unreleased/getting-started/design.html +++ b/docs/unreleased/getting-started/design.html @@ -380,8 +380,8 @@ and the others will become backups if the master should fail.</p> <p>The Accumulo Tracer process supports the distributed timing API provided by Accumulo. One to many of these processes can be run on a cluster which will write the timing -information to a given Accumulo table for future reference. Seeing the section on -Tracing for more information on this support.</p> +information to a given Accumulo table for future reference. See the +<a href="/docs/unreleased/administration/tracing">tracing documentation</a> for more information.</p> <h3 id="monitor">Monitor</h3> @@ -390,7 +390,7 @@ the state of an instance. The Monitor shows graphs and tables which contain info about read/write rates, cache hit/miss rates, and Accumulo table information such as scan rate and active/queued compactions. Additionally, the Monitor should always be the first point of entry when attempting to debug an Accumulo problem as it will show high-level problems -in addition to aggregated errors from all nodes in the cluster. See the <a href="/docs/unreleased/administration/overview#monitoring">Accumulo monitor documentation</a> +in addition to aggregated errors from all nodes in the cluster. See the <a href="/docs/unreleased/administration/monitoring-metrics#monitoring">Accumulo monitor documentation</a> for more information.</p> <p>Multiple Monitors can be run to provide hot-standby support in the face of failure. Due to the @@ -399,9 +399,8 @@ at one time. Leader election will be performed internally to choose the active M <h3 id="client">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> +<p>Accumulo has a client library that can be used to write applications that write and read +data to/from Accumulo. See the <a href="/docs/unreleased/getting-started/clients">Accumulo clients documentation</a> for more information.</p> <h2 id="data-management">Data Management</h2> @@ -439,7 +438,8 @@ performs Major Compactions of files within a tablet, in which some set of RFiles 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> +when the new file is created. See the <a href="/docs/unreleased/getting-started/table_configuration#compaction">compaction documentation</a> +for more information.</p> <h2 id="splitting">Splitting</h2> @@ -455,8 +455,8 @@ writes giving better initial performance without waiting for automatic splitting.</p> <p>As data is deleted from a table, tablets may shrink. Over time this can lead -to small or empty tablets. To deal with this, merging of tablets was -introduced in Accumulo 1.4. This is discussed in more detail later.</p> +to small or empty tablets. To deal with this, the <a href="/docs/unreleased/getting-started/table_configuration#merging-tablets">merging of tablets</a> +was introduced in Accumulo 1.4.</p> <h2 id="fault-tolerance">Fault-Tolerance</h2> http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/2c7f1e8c/docs/unreleased/getting-started/table_configuration.html ---------------------------------------------------------------------- diff --git a/docs/unreleased/getting-started/table_configuration.html b/docs/unreleased/getting-started/table_configuration.html index 8a691ca..ab36b45 100644 --- a/docs/unreleased/getting-started/table_configuration.html +++ b/docs/unreleased/getting-started/table_configuration.html @@ -320,18 +320,18 @@ <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, bloom filters, iterators, and block -cache. See the <a href="/docs/unreleased/config/">configuration documentation</a> for a complete list of -available configuration options.</p> +cache. See the <a href="/docs/unreleased/administration/configuration-properties">configuration properties documentation</a> for +a complete list of available configuration options.</p> <h2 id="locality-groups">Locality Groups</h2> <p>Accumulo supports storing sets of column families separately on disk to allow clients to efficiently scan over columns that are frequently used together 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 +<a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/Scanner.html";>Scanner</a> and <a href="https://static.javadoc.io/org.apache.accumulo/accumulo-core/1.8.1/org/apache/accumulo/core/client/BatchScanner.html";>BatchScanner</a> 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. +<p>By default, tables place all column families into the same <code class="highlighter-rouge">default</code> locality group. Additional locality groups can be configured at any time via the shell or programmatically as follows:</p> @@ -789,11 +789,8 @@ compact tablets that overlap the given row range.</p> <h3 id="compaction-strategies">Compaction Strategies</h3> <p>The default behavior of major compactions is defined in the class DefaultCompactionStrategy. -This behavior can be changed by overriding the following property with a fully qualified class name:</p> - -<div class="highlighter-rouge"><pre class="highlight"><code>table.majc.compaction.strategy -</code></pre> -</div> +This behavior can be changed by overriding <a href="/docs/unreleased/administration/configuration-properties#table_majc_compaction_strategy">table.majc.compaction.strategy</a> with a fully +qualified class name.</p> <p>Custom compaction strategies can have additional properties that are specified following the prefix property:</p> @@ -802,15 +799,15 @@ This behavior can be changed by overriding the following property with a fully q </div> <p>Accumulo provides a few classes that can be used as an alternative compaction strategy. These classes are located in the -org.apache.accumulo.tserver.compaction.* package. EverythingCompactionStrategy will simply compact all files. This is the -strategy used by the user âcompactâ command. SizeLimitCompactionStrategy compacts files no bigger than the limit set in the -property table.majc.compaction.strategy.opts.sizeLimit.</p> +<code class="highlighter-rouge">org.apache.accumulo.tserver.compaction.*</code> package. <code class="highlighter-rouge">EverythingCompactionStrategy</code> will simply compact all files. This is the +strategy used by the user <code class="highlighter-rouge">compact</code> command. <code class="highlighter-rouge">SizeLimitCompactionStrategy</code> compacts files no bigger than the limit set in the +property <code class="highlighter-rouge">table.majc.compaction.strategy.opts.sizeLimit</code>.</p> -<p>TwoTierCompactionStrategy is a hybrid compaction strategy that supports two types of compression. If the total size of -files being compacted is larger than table.majc.compaction.strategy.opts.file.large.compress.threshold than a larger -compression type will be used. The larger compression type is specified in table.majc.compaction.strategy.opts.file.large.compress.type. -Otherwise, the configured table compression will be used. To use this strategy with minor compactions set table.file.compress.type=snappy -and set a different compress type in table.majc.compaction.strategy.opts.file.large.compress.type for larger files.</p> +<p><code class="highlighter-rouge">TwoTierCompactionStrategy</code> is a hybrid compaction strategy that supports two types of compression. If the total size of +files being compacted is larger than <code class="highlighter-rouge">table.majc.compaction.strategy.opts.file.large.compress.threshold</code> than a larger +compression type will be used. The larger compression type is specified in <code class="highlighter-rouge">table.majc.compaction.strategy.opts.file.large.compress.type</code>. +Otherwise, the configured table compression will be used. To use this strategy with minor compactions set <code class="highlighter-rouge">table.file.compress.type=snappy</code> +and set a different compress type in <code class="highlighter-rouge">table.majc.compaction.strategy.opts.file.large.compress.type</code> for larger files.</p> <h2 id="pre-splitting-tables">Pre-splitting tables</h2> @@ -828,7 +825,7 @@ root@myinstance> addsplits -t newTable g n t </div> <p>This will create a new table with 4 tablets. The table will be split -on the letters <code class="highlighter-rouge">g'',</code>nââ, and ``tââ which will work nicely if the +on the letters <code class="highlighter-rouge">g</code>, <code class="highlighter-rouge">n</code>, and <code class="highlighter-rouge">t</code> which will work nicely if the row data start with lower-case alphabetic characters. If your row data includes binary information or numeric information, or if the distribution of the row information is not flat, then you would pick @@ -847,7 +844,7 @@ window of current information, tablets for older rows may be empty.</p> <p>Accumulo supports tablet merging, which can be used to reduce the number of split points. The following command will merge all rows -from <code class="highlighter-rouge">A'' to</code>Zââ into a single tablet:</p> +from <code class="highlighter-rouge">A</code> to <code class="highlighter-rouge">Z</code> into a single tablet:</p> <div class="highlighter-rouge"><pre class="highlight"><code>root@myinstance> merge -t myTable -s A -e Z </code></pre> @@ -891,7 +888,7 @@ root@myinstance> merge -t myTable <h2 id="delete-range">Delete Range</h2> <p>Consider an indexing scheme that uses date information in each row. -For example ``20110823-15:20:25.013ââ might be a row that specifies a +For example <code class="highlighter-rouge">20110823-15:20:25.013</code> might be a row that specifies a date and time. In some cases, we might like to delete rows based on this date, say to remove all the data older than the current year. Accumulo supports a delete range operation which efficiently @@ -901,8 +898,8 @@ removes data between two rows. For example:</p> </code></pre> </div> -<p>This will delete all rows starting with <code class="highlighter-rouge">2010'' and it will stop at -any row starting</code>2011ââ. You can delete any data prior to 2011 +<p>This will delete all rows starting with <code class="highlighter-rouge">2010</code> and it will stop at +any row starting <code class="highlighter-rouge">2011</code>. You can delete any data prior to 2011 with:</p> <div class="highlighter-rouge"><pre class="highlight"><code>root@myinstance> deleterange -t myTable -e 2011 --force http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/2c7f1e8c/feed.xml ---------------------------------------------------------------------- diff --git a/feed.xml b/feed.xml index 544c606..e090d54 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>Wed, 24 May 2017 17:38:31 -0400</pubDate> - <lastBuildDate>Wed, 24 May 2017 17:38:31 -0400</lastBuildDate> + <pubDate>Thu, 25 May 2017 10:21:12 -0400</pubDate> + <lastBuildDate>Thu, 25 May 2017 10:21:12 -0400</lastBuildDate> <generator>Jekyll v3.3.1</generator> <item>
