You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by ct...@apache.org on 2016/05/04 01:50:47 UTC
[1/2] accumulo git commit: Improve formatting for definition list in
glossary
Repository: accumulo
Updated Branches:
refs/heads/asf-site c40e208ab -> 987edc45d
refs/heads/gh-pages c59e3c060 -> 966e99581
Improve formatting for definition list in glossary
Project: http://git-wip-us.apache.org/repos/asf/accumulo/repo
Commit: http://git-wip-us.apache.org/repos/asf/accumulo/commit/966e9958
Tree: http://git-wip-us.apache.org/repos/asf/accumulo/tree/966e9958
Diff: http://git-wip-us.apache.org/repos/asf/accumulo/diff/966e9958
Branch: refs/heads/gh-pages
Commit: 966e9958135a5db06ea2915ebca8f28c57c0f20e
Parents: c59e3c0
Author: Christopher Tubbs <ct...@apache.org>
Authored: Tue May 3 19:47:37 2016 -0400
Committer: Christopher Tubbs <ct...@apache.org>
Committed: Tue May 3 19:47:37 2016 -0400
----------------------------------------------------------------------
glossary.md | 50 +++++++++++++++++++++++++-------------------------
1 file changed, 25 insertions(+), 25 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/accumulo/blob/966e9958/glossary.md
----------------------------------------------------------------------
diff --git a/glossary.md b/glossary.md
index 4b8761e..54b3ae7 100644
--- a/glossary.md
+++ b/glossary.md
@@ -5,59 +5,59 @@ nav: nav_glossary
authorizations
-: a set of strings associated with a user or with a particular scan that will
+: > a set of strings associated with a user or with a particular scan that will
be used to determine which key/value pairs are visible to the user.
cell
-: a set of key/value pairs whose keys differ only in timestamp.
+: > a set of key/value pairs whose keys differ only in timestamp.
column
-: the portion of the key that sorts after the row and is divided into family,
+: > the portion of the key that sorts after the row and is divided into family,
qualifier, and visibility.
column family
-: the portion of the key that sorts second and controls locality groups, the
+: > the portion of the key that sorts second and controls locality groups, the
row/column hybrid nature of accumulo.
column qualifier
-: the portion of the key that sorts third and provides additional key
+: > the portion of the key that sorts third and provides additional key
uniqueness.
column visibility
-: the portion of the key that sorts fourth and controls user access to
+: > the portion of the key that sorts fourth and controls user access to
individual key/value pairs. Visibilities are boolean AND (&) and OR (|)
combinations of authorization strings with parentheses required to determine
ordering, e.g. (AB&C)|DEF.
iterator
-: a mechanism for modifying tablet-local portions of the key/value space.
+: > a mechanism for modifying tablet-local portions of the key/value space.
Iterators are used for standard administrative tasks as well as for custom
processing.
iterator priority
-: an iterator must be configured with a particular scope and priority. When a
+: > an iterator must be configured with a particular scope and priority. When a
tablet server enters that scope, it will instantiate iterators in priority
order starting from the smallest priority and ending with the largest, and
apply each to the data read before rewriting the data or sending the data to
the user.
iterator scopes
-: the possible scopes for iterators are where the tablet server is already
+: > the possible scopes for iterators are where the tablet server is already
reading and/or writing data: minor compaction / flush time (*minc*
scope), major compaction / file merging time (*majc* scope), and query
time (*scan* scope).
gc
-: process that identifies temporary files in HDFS that are no longer needed by
+: > process that identifies temporary files in HDFS that are no longer needed by
any process, and deletes them.
key
-: the key into the distributed sorted map which is accumulo. The key is
+: > the key into the distributed sorted map which is accumulo. The key is
subdivided into row, column, and timestamp. The column is further divided into
family, qualifier, and visibility.
locality group
-: a set of column families that will be grouped together on disk. With no
+: > a set of column families that will be grouped together on disk. With no
locality groups configured, data is stored on disk in row order. If each
column family were configured to be its own locality group, the data for each
column would be stored separately, in row order. Configuring sets of columns
@@ -65,60 +65,60 @@ into locality groups is a compromise between the two approaches and will
improve performance when multiple columns are accessed in the same scan.
log-structured merge-tree
-: the sorting / flushing / merging scheme on which BigTable's design is based.
+: > the sorting / flushing / merging scheme on which BigTable's design is based.
logger
-: in 1.4 and older, process that accepts updates to tablet servers and writes
+: > in 1.4 and older, process that accepts updates to tablet servers and writes
them to local on-disk storage for redundancy. in 1.5 the functionality was
subsumed by the tablet server and datanode with HDFS writes.
major compaction
-: merging multiple files into a single file. If all of a tablet's files are
+: > merging multiple files into a single file. If all of a tablet's files are
merged into a single file, it is called a *full major compaction*.
master
-: process that detects and responds to tablet failures, balances load across
+: > process that detects and responds to tablet failures, balances load across
tablet servers by assigning and migrating tablets when required, coordinates
table operations, and handles tablet server logistics (startup, shutdown,
recovery).
minor compaction
-: flushing data from memory to disk. Usually this creates a new file for a
+: > flushing data from memory to disk. Usually this creates a new file for a
tablet, but if the memory flushed is merge-sorted in with data from an existing
file (replacing that file), it is called a *merging minor compaction*.
monitor
-: process that displays status and usage information for all Accumulo
+: > process that displays status and usage information for all Accumulo
components.
permissions
-: administrative abilities that must be given to a user such as creating tables
+: > administrative abilities that must be given to a user such as creating tables
or users and changing permissions or configuration parameters.
row
-: the portion of the key that controls atomicity. Keys with the same row are
+: > the portion of the key that controls atomicity. Keys with the same row are
guaranteed to remain on a single tablet hosted by a single tablet server,
therefore multiple key/value pairs can be added to or removed from a row at the
same time. The row is used for the primary sorting of the key.
scan
-: reading a range of key/value pairs.
+: > reading a range of key/value pairs.
tablet
-: a contiguous key range; the unit of work for a tablet server.
+: > a contiguous key range; the unit of work for a tablet server.
tablet servers
-: a set of servers that hosts reads and writes for tablets. Each server hosts
+: > a set of servers that hosts reads and writes for tablets. Each server hosts
a distinct set of tablets at any given time, but the tablets may be hosted by
different servers over time.
timestamp
-: the portion of the key that controls versioning. Otherwise identical keys
+: > the portion of the key that controls versioning. Otherwise identical keys
with differing timestamps are considered to be versions of a single
*cell*. Accumulo can be configured to keep the *N* newest
versions of each *cell*. When a deletion entry is inserted, it deletes
all earlier versions for its cell.
value
-: immutable bytes associated with a particular key.
+: > immutable bytes associated with a particular key.
[2/2] accumulo git commit: Jekyll build from gh-pages:966e995
Posted by ct...@apache.org.
Jekyll build from gh-pages:966e995
Improve formatting for definition list in glossary
Project: http://git-wip-us.apache.org/repos/asf/accumulo/repo
Commit: http://git-wip-us.apache.org/repos/asf/accumulo/commit/987edc45
Tree: http://git-wip-us.apache.org/repos/asf/accumulo/tree/987edc45
Diff: http://git-wip-us.apache.org/repos/asf/accumulo/diff/987edc45
Branch: refs/heads/asf-site
Commit: 987edc45d8d3a3340d2b47d38735092c725c9e24
Parents: c40e208
Author: Christopher Tubbs <ct...@apache.org>
Authored: Tue May 3 19:47:37 2016 -0400
Committer: Christopher Tubbs <ct...@apache.org>
Committed: Tue May 3 19:47:53 2016 -0400
----------------------------------------------------------------------
feed.xml | 4 +-
glossary.html | 190 ++++++++++++++++++++++++++++++++++++++++-------------
2 files changed, 147 insertions(+), 47 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/accumulo/blob/987edc45/feed.xml
----------------------------------------------------------------------
diff --git a/feed.xml b/feed.xml
index b9828b5..8f691f2 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>Tue, 03 May 2016 18:44:26 -0400</pubDate>
- <lastBuildDate>Tue, 03 May 2016 18:44:26 -0400</lastBuildDate>
+ <pubDate>Tue, 03 May 2016 19:47:49 -0400</pubDate>
+ <lastBuildDate>Tue, 03 May 2016 19:47:49 -0400</lastBuildDate>
<generator>Jekyll v3.0.3</generator>
</channel>
http://git-wip-us.apache.org/repos/asf/accumulo/blob/987edc45/glossary.html
----------------------------------------------------------------------
diff --git a/glossary.html b/glossary.html
index 6376d6b..aa7070a 100644
--- a/glossary.html
+++ b/glossary.html
@@ -240,98 +240,198 @@
<dl>
<dt>authorizations</dt>
- <dd>a set of strings associated with a user or with a particular scan that will
-be used to determine which key/value pairs are visible to the user.</dd>
+ <dd>
+ <blockquote>
+ <p>a set of strings associated with a user or with a particular scan that will
+be used to determine which key/value pairs are visible to the user.</p>
+ </blockquote>
+ </dd>
<dt>cell</dt>
- <dd>a set of key/value pairs whose keys differ only in timestamp.</dd>
+ <dd>
+ <blockquote>
+ <p>a set of key/value pairs whose keys differ only in timestamp.</p>
+ </blockquote>
+ </dd>
<dt>column</dt>
- <dd>the portion of the key that sorts after the row and is divided into family,
-qualifier, and visibility.</dd>
+ <dd>
+ <blockquote>
+ <p>the portion of the key that sorts after the row and is divided into family,
+qualifier, and visibility.</p>
+ </blockquote>
+ </dd>
<dt>column family</dt>
- <dd>the portion of the key that sorts second and controls locality groups, the
-row/column hybrid nature of accumulo.</dd>
+ <dd>
+ <blockquote>
+ <p>the portion of the key that sorts second and controls locality groups, the
+row/column hybrid nature of accumulo.</p>
+ </blockquote>
+ </dd>
<dt>column qualifier</dt>
- <dd>the portion of the key that sorts third and provides additional key
-uniqueness.</dd>
+ <dd>
+ <blockquote>
+ <p>the portion of the key that sorts third and provides additional key
+uniqueness.</p>
+ </blockquote>
+ </dd>
<dt>column visibility</dt>
- <dd>the portion of the key that sorts fourth and controls user access to
+ <dd>
+ <blockquote>
+ <p>the portion of the key that sorts fourth and controls user access to
individual key/value pairs. Visibilities are boolean AND (&) and OR (|)
combinations of authorization strings with parentheses required to determine
-ordering, e.g. (AB&C)|DEF.</dd>
+ordering, e.g. (AB&C)|DEF.</p>
+ </blockquote>
+ </dd>
<dt>iterator</dt>
- <dd>a mechanism for modifying tablet-local portions of the key/value space.
+ <dd>
+ <blockquote>
+ <p>a mechanism for modifying tablet-local portions of the key/value space.
Iterators are used for standard administrative tasks as well as for custom
-processing.</dd>
+processing.</p>
+ </blockquote>
+ </dd>
<dt>iterator priority</dt>
- <dd>an iterator must be configured with a particular scope and priority. When a
+ <dd>
+ <blockquote>
+ <p>an iterator must be configured with a particular scope and priority. When a
tablet server enters that scope, it will instantiate iterators in priority
order starting from the smallest priority and ending with the largest, and
apply each to the data read before rewriting the data or sending the data to
-the user.</dd>
+the user.</p>
+ </blockquote>
+ </dd>
<dt>iterator scopes</dt>
- <dd>the possible scopes for iterators are where the tablet server is already
+ <dd>
+ <blockquote>
+ <p>the possible scopes for iterators are where the tablet server is already
reading and/or writing data: minor compaction / flush time (<em>minc</em>
scope), major compaction / file merging time (<em>majc</em> scope), and query
-time (<em>scan</em> scope).</dd>
+time (<em>scan</em> scope).</p>
+ </blockquote>
+ </dd>
<dt>gc</dt>
- <dd>process that identifies temporary files in HDFS that are no longer needed by
-any process, and deletes them.</dd>
+ <dd>
+ <blockquote>
+ <p>process that identifies temporary files in HDFS that are no longer needed by
+any process, and deletes them.</p>
+ </blockquote>
+ </dd>
<dt>key</dt>
- <dd>the key into the distributed sorted map which is accumulo. The key is
+ <dd>
+ <blockquote>
+ <p>the key into the distributed sorted map which is accumulo. The key is
subdivided into row, column, and timestamp. The column is further divided into
-family, qualifier, and visibility.</dd>
+family, qualifier, and visibility.</p>
+ </blockquote>
+ </dd>
<dt>locality group</dt>
- <dd>a set of column families that will be grouped together on disk. With no
+ <dd>
+ <blockquote>
+ <p>a set of column families that will be grouped together on disk. With no
locality groups configured, data is stored on disk in row order. If each
column family were configured to be its own locality group, the data for each
column would be stored separately, in row order. Configuring sets of columns
into locality groups is a compromise between the two approaches and will
-improve performance when multiple columns are accessed in the same scan.</dd>
+improve performance when multiple columns are accessed in the same scan.</p>
+ </blockquote>
+ </dd>
<dt>log-structured merge-tree</dt>
- <dd>the sorting / flushing / merging scheme on which BigTable\u2019s design is based.</dd>
+ <dd>
+ <blockquote>
+ <p>the sorting / flushing / merging scheme on which BigTable\u2019s design is based.</p>
+ </blockquote>
+ </dd>
<dt>logger</dt>
- <dd>in 1.4 and older, process that accepts updates to tablet servers and writes
+ <dd>
+ <blockquote>
+ <p>in 1.4 and older, process that accepts updates to tablet servers and writes
them to local on-disk storage for redundancy. in 1.5 the functionality was
-subsumed by the tablet server and datanode with HDFS writes.</dd>
+subsumed by the tablet server and datanode with HDFS writes.</p>
+ </blockquote>
+ </dd>
<dt>major compaction</dt>
- <dd>merging multiple files into a single file. If all of a tablet\u2019s files are
-merged into a single file, it is called a <em>full major compaction</em>.</dd>
+ <dd>
+ <blockquote>
+ <p>merging multiple files into a single file. If all of a tablet\u2019s files are
+merged into a single file, it is called a <em>full major compaction</em>.</p>
+ </blockquote>
+ </dd>
<dt>master</dt>
- <dd>process that detects and responds to tablet failures, balances load across
+ <dd>
+ <blockquote>
+ <p>process that detects and responds to tablet failures, balances load across
tablet servers by assigning and migrating tablets when required, coordinates
table operations, and handles tablet server logistics (startup, shutdown,
-recovery).</dd>
+recovery).</p>
+ </blockquote>
+ </dd>
<dt>minor compaction</dt>
- <dd>flushing data from memory to disk. Usually this creates a new file for a
+ <dd>
+ <blockquote>
+ <p>flushing data from memory to disk. Usually this creates a new file for a
tablet, but if the memory flushed is merge-sorted in with data from an existing
-file (replacing that file), it is called a <em>merging minor compaction</em>.</dd>
+file (replacing that file), it is called a <em>merging minor compaction</em>.</p>
+ </blockquote>
+ </dd>
<dt>monitor</dt>
- <dd>process that displays status and usage information for all Accumulo
-components.</dd>
+ <dd>
+ <blockquote>
+ <p>process that displays status and usage information for all Accumulo
+components.</p>
+ </blockquote>
+ </dd>
<dt>permissions</dt>
- <dd>administrative abilities that must be given to a user such as creating tables
-or users and changing permissions or configuration parameters.</dd>
+ <dd>
+ <blockquote>
+ <p>administrative abilities that must be given to a user such as creating tables
+or users and changing permissions or configuration parameters.</p>
+ </blockquote>
+ </dd>
<dt>row</dt>
- <dd>the portion of the key that controls atomicity. Keys with the same row are
+ <dd>
+ <blockquote>
+ <p>the portion of the key that controls atomicity. Keys with the same row are
guaranteed to remain on a single tablet hosted by a single tablet server,
therefore multiple key/value pairs can be added to or removed from a row at the
-same time. The row is used for the primary sorting of the key.</dd>
+same time. The row is used for the primary sorting of the key.</p>
+ </blockquote>
+ </dd>
<dt>scan</dt>
- <dd>reading a range of key/value pairs.</dd>
+ <dd>
+ <blockquote>
+ <p>reading a range of key/value pairs.</p>
+ </blockquote>
+ </dd>
<dt>tablet</dt>
- <dd>a contiguous key range; the unit of work for a tablet server.</dd>
+ <dd>
+ <blockquote>
+ <p>a contiguous key range; the unit of work for a tablet server.</p>
+ </blockquote>
+ </dd>
<dt>tablet servers</dt>
- <dd>a set of servers that hosts reads and writes for tablets. Each server hosts
+ <dd>
+ <blockquote>
+ <p>a set of servers that hosts reads and writes for tablets. Each server hosts
a distinct set of tablets at any given time, but the tablets may be hosted by
-different servers over time.</dd>
+different servers over time.</p>
+ </blockquote>
+ </dd>
<dt>timestamp</dt>
- <dd>the portion of the key that controls versioning. Otherwise identical keys
+ <dd>
+ <blockquote>
+ <p>the portion of the key that controls versioning. Otherwise identical keys
with differing timestamps are considered to be versions of a single
<em>cell</em>. Accumulo can be configured to keep the <em>N</em> newest
versions of each <em>cell</em>. When a deletion entry is inserted, it deletes
-all earlier versions for its cell.</dd>
+all earlier versions for its cell.</p>
+ </blockquote>
+ </dd>
<dt>value</dt>
- <dd>immutable bytes associated with a particular key.</dd>
+ <dd>
+ <blockquote>
+ <p>immutable bytes associated with a particular key.</p>
+ </blockquote>
+ </dd>
</dl>