# accumulo-commits mailing list archives

##### Site index · List index
Message view
Top
From e..@apache.org
Subject svn commit: r1208726 - in /incubator/accumulo/trunk/docs: ./ examples/ src/user_manual/chapters/
Date Wed, 30 Nov 2011 19:40:38 GMT
Author: ecn
Date: Wed Nov 30 19:40:36 2011
New Revision: 1208726

URL: http://svn.apache.org/viewvc?rev=1208726&view=rev
Log:
ACCUMULO-165: fix speling

Modified:
incubator/accumulo/trunk/docs/bulkIngest.html
incubator/accumulo/trunk/docs/isolation.html
incubator/accumulo/trunk/docs/metrics.html
incubator/accumulo/trunk/docs/src/user_manual/chapters/analytics.tex
incubator/accumulo/trunk/docs/src/user_manual/chapters/high_speed_ingest.tex
incubator/accumulo/trunk/docs/src/user_manual/chapters/security.tex

==============================================================================
+++ incubator/accumulo/trunk/docs/administration.html Wed Nov 30 19:40:36 2011
@@ -28,8 +28,8 @@
<p>For the most part, accumulo is ready to go out of the box. To start it, first you
must distribute and install
the accumulo software to each machine in the cloud that you wish to run on. The software
should be installed
in the same directory on each machine and configured identically (or at least similarly...
see the configuration
-sections for more details). Select one machine to be your boostrap machine, the one that
you will start accumulo
machine. On this machine,
+sections for more details). Select one machine to be your bootstrap machine, the one that
you will start accumulo
machine. On this machine,
create a conf/masters and conf/slaves file. In the masters file, type the hostname of the
machine you wish to run the master on (probably localhost).
In the slaves file, type the hostnames, separated by newlines of each machine you wish to
participate in accumulo as a tablet server. If you neglect
to create these files, the startup scripts will assume you are trying to run on localhost
only, and will instantiate a single-node instance only.
@@ -88,7 +88,7 @@ servers use.  In accumulo-env.sh there i
ACCUMULO_TSERVER_OPTS.  By default this is set to something like "-Xmx512m
-Xms512m".  These are Java jvm options asking Java to use 512 megabytes of
memory.  By default accumulo stores data written to it outside of the Java
-memory space inorder to avoid pauses caused by the Java garbage collector.  The
+memory space in order to avoid pauses caused by the Java garbage collector.  The
amount of memory it uses for this data is determined by the accumulo setting
"tserver.memory.maps.max".  Since this memory is outside of the Java managed
memory, the process can grow larger than the -Xmx setting.  So if -Xmx is set

Modified: incubator/accumulo/trunk/docs/bulkIngest.html
URL: http://svn.apache.org/viewvc/incubator/accumulo/trunk/docs/bulkIngest.html?rev=1208726&r1=1208725&r2=1208726&view=diff
==============================================================================
--- incubator/accumulo/trunk/docs/bulkIngest.html (original)
+++ incubator/accumulo/trunk/docs/bulkIngest.html Wed Nov 30 19:40:36 2011
@@ -57,7 +57,7 @@ when range partitioning using a tables s
get one map file.

<P>Any set of cut points for range partitioning can be used in a map
-reduce job, but using Accumulos current splits is probably the most
+reduce job, but using Accumulo's current splits is probably the most
optimal thing to do.  However in some case there may be too many
splits.  For example if there are 2000 splits, you would need to run
2001 reducers.  To overcome this problem use the

==============================================================================
+++ incubator/accumulo/trunk/docs/examples/README.dirlist Wed Nov 30 19:40:36 2011
@@ -54,7 +54,7 @@ To perform searches on file or directory
$./bin/accumulo org.apache.accumulo.examples.dirlist.QueryUtil instance zookeepers username password indexTable exampleVis '*jar' -search$ ./bin/accumulo org.apache.accumulo.examples.dirlist.QueryUtil instance zookeepers username

-To count the number of direct children (directories and files) and descendants (children
and children's descendents, directories and files), run the FileCount over the dirTable table.
+To count the number of direct children (directories and files) and descendants (children
and children's descendants, directories and files), run the FileCount over the dirTable table.
The results are written back to the same table.

\$ ./bin/accumulo org.apache.accumulo.examples.dirlist.FileCount instance zookeepers username

Modified: incubator/accumulo/trunk/docs/isolation.html
URL: http://svn.apache.org/viewvc/incubator/accumulo/trunk/docs/isolation.html?rev=1208726&r1=1208725&r2=1208726&view=diff
==============================================================================
--- incubator/accumulo/trunk/docs/isolation.html (original)
+++ incubator/accumulo/trunk/docs/isolation.html Wed Nov 30 19:40:36 2011
@@ -31,9 +31,9 @@
<li>iterators executed as part of a minor or major compaction
<li>bulk import of new files
</ul>
-Isolation garuantees that either all or none of the changes made by these operations on a
row are seen.  Use the <a href='apidocs/org/apache/accumulo/core/client/IsolatedScanner.html'>IsolatedScanner</a>
to obtain an isolated view of a accumulo table.  When using the regular scanner it is possible
to see a non isolated view of a row.  For example if a mutation modifies three columns, it
is possible that you will only see two of those modifications.  With the isolated scanner
either all three of the changes are seen or none.  For an example of this try running the
<a href='apidocs/org/apache/accumulo/examples/isolation/InterferenceTest.html'>InterferenceTest</a>
example.
+Isolation guarantees that either all or none of the changes made by these operations on a
row are seen.  Use the <a href='apidocs/org/apache/accumulo/core/client/IsolatedScanner.html'>IsolatedScanner</a>
to obtain an isolated view of a accumulo table.  When using the regular scanner it is possible
to see a non isolated view of a row.  For example if a mutation modifies three columns, it
is possible that you will only see two of those modifications.  With the isolated scanner
either all three of the changes are seen or none.  For an example of this try running the
<a href='apidocs/org/apache/accumulo/examples/isolation/InterferenceTest.html'>InterferenceTest</a>
example.

<p>At this time there is no client side isolation support for the <a href='apidocs/org/apache/accumulo/core/client/BatchScanner.html'>BatchScanner</a>.
You may consider using the <a href='apidocs/org/apache/accumulo/core/iterators/WholeRowIterator.html'>WholeRowIterator</a>
with the  <a href='apidocs/org/apache/accumulo/core/client/BatchScanner.html'>BatchScanner</a>
to achieve isolation though. This drawback of doing this is that entire rows are read into
memory on the server side.  If a row is too big, it may crash a tablet server.  The <a
href='apidocs/org/apache/accumulo/core/client/IsolatedScanner.html'>IsolatedScanner</a>
buffers rows on the client side so a large row will not crash a tablet server.

<h3>Iterators</h3>
-<p>When writing server side iterators for accumulo isolation is something to be aware
of.  A scan time iterator in accumulo reads from a set of data sources.  While an iterator
is reading data it has an isolated view.  However, after it returns a key/value it is possible
that accumulo may switch data sources and re-seek the iterator.  This is done so that resources
may be reclaimed.  When the user does not request isolation this can occur after any key is
returned.  When a user request isolation this will only occur after a new row is returned,
in which case it will reseek to the very beginning of the next possible row.
+<p>When writing server side iterators for accumulo isolation is something to be aware
of.  A scan time iterator in accumulo reads from a set of data sources.  While an iterator
is reading data it has an isolated view.  However, after it returns a key/value it is possible
that accumulo may switch data sources and re-seek the iterator.  This is done so that resources
may be reclaimed.  When the user does not request isolation this can occur after any key is
returned.  When a user request isolation this will only occur after a new row is returned,
in which case it will re-seek to the very beginning of the next possible row.

Modified: incubator/accumulo/trunk/docs/metrics.html
URL: http://svn.apache.org/viewvc/incubator/accumulo/trunk/docs/metrics.html?rev=1208726&r1=1208725&r2=1208726&view=diff
==============================================================================
--- incubator/accumulo/trunk/docs/metrics.html (original)
+++ incubator/accumulo/trunk/docs/metrics.html Wed Nov 30 19:40:36 2011
@@ -32,7 +32,7 @@ Except where specified all time values a
<tbody>
<tr class="highlight"><td>public long getPingCount();</td><td>Number
of pings to tablet servers</td></tr>
-		<tr><td>public long getPingAvgTime();</td><td>Avergage time for
each ping</td></tr>
+		<tr><td>public long getPingAvgTime();</td><td>Average time for
each ping</td></tr>
<tr class="highlight"><td>public long getPingMinTime();</td><td>Minimum
time for each ping</td></tr>
<tr><td>public long getPingMaxTime();</td><td>Maximum time for
each ping</td></tr>
<tr class="highlight"><td>public String getTServerWithHighestPingTime();</td><td>tablet
server with highest ping</td></tr>

==============================================================================
+++ incubator/accumulo/trunk/docs/src/user_manual/chapters/administration.tex Wed Nov 30 19:40:36
2011
@@ -69,7 +69,7 @@ files.

\subsection{Edit conf/accumulo-env.sh}

-Accumulo needs to know where to find the software it depends on. Edit accumuloenv.
+Accumulo needs to know where to find the software it depends on. Edit accumulo-env.
sh and specify the following:

\begin{enumerate}

Modified: incubator/accumulo/trunk/docs/src/user_manual/chapters/analytics.tex
URL: http://svn.apache.org/viewvc/incubator/accumulo/trunk/docs/src/user_manual/chapters/analytics.tex?rev=1208726&r1=1208725&r2=1208726&view=diff
==============================================================================
--- incubator/accumulo/trunk/docs/src/user_manual/chapters/analytics.tex (original)
+++ incubator/accumulo/trunk/docs/src/user_manual/chapters/analytics.tex Wed Nov 30 19:40:36
2011
@@ -164,7 +164,7 @@ MapReduce jobs.

All that is needed to aggregate values of a table is to identify the fields over which
values will be grouped, insert mutations with those fields as the key, and configure
-the table with a combining iterator that supports the summarization operation
+the table with a combining iterator that supports the summarizing operation
desired.

The only restriction on an combining iterator is that the combiner developer

Modified: incubator/accumulo/trunk/docs/src/user_manual/chapters/high_speed_ingest.tex
URL: http://svn.apache.org/viewvc/incubator/accumulo/trunk/docs/src/user_manual/chapters/high_speed_ingest.tex?rev=1208726&r1=1208725&r2=1208726&view=diff
==============================================================================
--- incubator/accumulo/trunk/docs/src/user_manual/chapters/high_speed_ingest.tex (original)
+++ incubator/accumulo/trunk/docs/src/user_manual/chapters/high_speed_ingest.tex Wed Nov 30
19:40:36 2011
@@ -122,7 +122,7 @@ file is imported, but whenever it is rea
time is obtained and always used by the specialized system iterator to set that
time.

-The timestamp asigned by accumulo will be the same for every key in the file.
+The timestamp assigned by accumulo will be the same for every key in the file.
This could cause problems if the file contains multiple keys that are identical
except for the timestamp.  In this case, the sort order of the keys will be
undefined. This could occur if an insert and an update were in the same bulk

Modified: incubator/accumulo/trunk/docs/src/user_manual/chapters/security.tex
URL: http://svn.apache.org/viewvc/incubator/accumulo/trunk/docs/src/user_manual/chapters/security.tex?rev=1208726&r1=1208725&r2=1208726&view=diff
==============================================================================
--- incubator/accumulo/trunk/docs/src/user_manual/chapters/security.tex (original)
+++ incubator/accumulo/trunk/docs/src/user_manual/chapters/security.tex Wed Nov 30 19:40:36
2011
@@ -126,7 +126,7 @@ config -t table -s table.constraint.1=or

Any user with the alter table permission can add or remove this constraint.
This constraint is not applied to bulk imported data, if this a concern then
-disable the bulk import pesmission.
+disable the bulk import permission.

\section{Secure Authorizations Handling}

@@ -134,7 +134,7 @@ For applications serving many users, it
will be created for each application user.  In this case a accumulo user with
all authorizations needed by any of the applications users must be created.  To
service queries, the application should create a scanner with the application
-users authorizations.  These authorizations could be obtined from a trusted 3rd
+users authorizations.  These authorizations could be obtained from a trusted 3rd
party.

Often production systems will integrate with Public-Key Infrastructure (PKI) and


Mime
View raw message