You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2018/08/29 18:40:48 UTC
[GitHub] mikewalch closed pull request #104: Spelling corrections for
Accumulo Website
mikewalch closed pull request #104: Spelling corrections for Accumulo Website
URL: https://github.com/apache/accumulo-website/pull/104
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/README.md b/README.md
index 3cd54980..e2cd4ce9 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/_docs-2-0/administration/caching.md b/_docs-2-0/administration/caching.md
index c516dc68..c04bc6e6 100644
--- a/_docs-2-0/administration/caching.md
+++ b/_docs-2-0/administration/caching.md
@@ -24,11 +24,11 @@ The index and data block caches are configured for tables by the following prope
* {% plink table.cache.index.enable %} - enables index block cache on the table (default is `true`)
While the index block cache is enabled by default for all Accumulo tables, users must enable the data block cache by
-settting {% plink table.cache.block.enable %} to `true` in the shell:
+setting {% plink table.cache.block.enable %} to `true` in the shell:
config -t mytable -s table.cache.block.enable=true
-Or programatically using [TableOperations.setProperty()][tableops]:
+Or programmatically using [TableOperations.setProperty()][tableops]:
```java
conn.tableOperations().setProperty("mytable", "table.cache.block.enable", "true");
diff --git a/_docs-2-0/administration/in-depth-install.md b/_docs-2-0/administration/in-depth-install.md
index ded15a87..8e6f5605 100644
--- a/_docs-2-0/administration/in-depth-install.md
+++ b/_docs-2-0/administration/in-depth-install.md
@@ -295,7 +295,7 @@ will expect the KeyStore in the same location.
### Client Configuration
Accumulo clients are configured in a different way than Accumulo servers. Clients are
-configured when [an Accumulo Connnector is created][client-conn] using Java builder methods
+configured when [an Accumulo Connector is created][client-conn] using Java builder methods
or a `accumulo-client.properties` file containing [client properties][client-props].
### Custom Table Tags
diff --git a/_docs-2-0/administration/kerberos.md b/_docs-2-0/administration/kerberos.md
index f6d6d403..91e04cd2 100644
--- a/_docs-2-0/administration/kerberos.md
+++ b/_docs-2-0/administration/kerberos.md
@@ -358,7 +358,7 @@ required to set up the SASL transport.
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.
+interact with the system.
While this example logs in via `kinit` with a password, any login method that caches Kerberos tickets
should work.
diff --git a/_docs-2-0/development/summaries.md b/_docs-2-0/development/summaries.md
index 4174fb17..d68a570e 100644
--- a/_docs-2-0/development/summaries.md
+++ b/_docs-2-0/development/summaries.md
@@ -124,10 +124,10 @@ statistics created by the CountingSummarizer that VisibilitySummarizer extends.
tooMany = 0
VisibilitySummarizer has an option `maxCounters` 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 `tooMany` statistic is 4. This is the number of
-visibilites that were not counted.
+visibilities and now the `tooMany` statistic is 4. This is the number of
+visibilities that were not counted.
```
root@uno summary_test> config -t summary_test -s table.summarizer.vis.opt.maxCounters=3
diff --git a/_docs-2-0/getting-started/clients.md b/_docs-2-0/getting-started/clients.md
index e6684ae5..3cab9e6c 100644
--- a/_docs-2-0/getting-started/clients.md
+++ b/_docs-2-0/getting-started/clients.md
@@ -191,9 +191,9 @@ These levels are:
Durability can be set in multiple ways:
1. The default durability of a table can be set in the Accumulo shell
-2. When creating a [Connector], the default durability can be overriden using `withBatchWriterConfig()`
+2. When creating a [Connector], the default durability can be overridden using `withBatchWriterConfig()`
or by setting [batch.writer.durability] in `accumulo-client.properties`.
-3. When a BatchWriter or ConditionalWriter is created, the durability settings above will be overriden
+3. When a BatchWriter or ConditionalWriter is created, the durability settings above will be overridden
by the `BatchWriterConfig` that is passed in.
```java
diff --git a/_docs-2-0/getting-started/design.md b/_docs-2-0/getting-started/design.md
index 4d758b77..70c3aa6f 100644
--- a/_docs-2-0/getting-started/design.md
+++ b/_docs-2-0/getting-started/design.md
@@ -131,7 +131,7 @@ RFile (short for Relative Key File) is a file that contains Accumulo's sorted ke
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.
diff --git a/_docs-2-0/getting-started/table_configuration.md b/_docs-2-0/getting-started/table_configuration.md
index a5289fb3..b2cbb566 100644
--- a/_docs-2-0/getting-started/table_configuration.md
+++ b/_docs-2-0/getting-started/table_configuration.md
@@ -664,7 +664,7 @@ One of the files is a list of files to distcp as shown below.
```
Before the table can be imported, it must be copied using `distcp`. After the
-`distcp` completea, the cloned table may be deleted.
+`distcp` completes, the cloned table may be deleted.
```
$ hadoop distcp -f /tmp/table1_export/distcp.txt /tmp/table1_export_dest
diff --git a/_posts/blog/2018-03-22-view-metrics-in-grafana.md b/_posts/blog/2018-03-22-view-metrics-in-grafana.md
index c99031bd..18b82917 100644
--- a/_posts/blog/2018-03-22-view-metrics-in-grafana.md
+++ b/_posts/blog/2018-03-22-view-metrics-in-grafana.md
@@ -7,7 +7,7 @@ The [Accumulo monitor][monitor] provides the easiest way to view Accumulo metric
1. The overview page is limited to 10 graphs
1. These graphs only show metrics for the past two hours
-The Accumulo monitor could be improved to be better a visualizaiton tool for metrics but this doesn't make
+The Accumulo monitor could be improved to be better a visualization tool for metrics but this doesn't make
sense when tools like [Grafana], [Graphite], and [Ganglia] exist and Accumulo can report metrics to these tools
using [Hadoop Metrics2][metrics2]. 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/_posts/release/2017-09-05-accumulo-2.0.0.md b/_posts/release/2017-09-05-accumulo-2.0.0.md
index caa93605..590b69f4 100644
--- a/_posts/release/2017-09-05-accumulo-2.0.0.md
+++ b/_posts/release/2017-09-05-accumulo-2.0.0.md
@@ -21,7 +21,7 @@ easier to use. The number of scripts in the `bin` directory of the Accumulo rele
has been reduced from 20 scripts to the four scripts below:
* `accumulo` - mostly left alone except for improved usage
-* `accumulo-service` - manage Accumulo processes as servcies
+* `accumulo-service` - manage Accumulo processes as services
* `accumulo-cluster` - manage Accumulo on cluster. Replaces `start-all.sh` and `stop-all.sh`
* `accumulo-util` - combines many utility scripts into one script.
diff --git a/_posts/release/2018-04-23-accumulo-1.9.0.md b/_posts/release/2018-04-23-accumulo-1.9.0.md
index ca7364fe..cb0bcd66 100644
--- a/_posts/release/2018-04-23-accumulo-1.9.0.md
+++ b/_posts/release/2018-04-23-accumulo-1.9.0.md
@@ -4,7 +4,7 @@ archived_critical: true
---
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
@@ -32,7 +32,7 @@ works in 2.0.0.
### Performance Improvements
Accumulo was profiled while running lots of concurrent small scans. During this
-excercise these performance bugs were found and fixed: [#379], [ACCUMULO-4778],
+exercise these performance bugs were found and fixed: [#379], [ACCUMULO-4778],
[ACCUMULO-4779], [ACCUMULO-4781], [ACCUMULO-4782], [ACCUMULO-4788],
[ACCUMULO-4789], [ACCUMULO-4790], [ACCUMULO-4797], [ACCUMULO-4798],
[ACCUMULO-4799], [ACCUMULO-4800], [ACCUMULO-4801], [ACCUMULO-4805], and
diff --git a/_posts/release/2018-05-14-accumulo-1.9.1.md b/_posts/release/2018-05-14-accumulo-1.9.1.md
index 21ec1e57..5e961a9e 100644
--- a/_posts/release/2018-05-14-accumulo-1.9.1.md
+++ b/_posts/release/2018-05-14-accumulo-1.9.1.md
@@ -33,7 +33,7 @@ risk from these bugs, which occur during automated recovery from such failures.
## Some WAL recovery files were not being properly cleaned up
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 [#432].
## Other Changes
diff --git a/contributor/contributors-guide.md b/contributor/contributors-guide.md
index bf3cbae2..8657f6c9 100644
--- a/contributor/contributors-guide.md
+++ b/contributor/contributors-guide.md
@@ -500,7 +500,7 @@ are the one who knows that this zero-length change in content is correct!
Accumulo primarily uses GitHub (via pull requests) for code reviews, but has access to an instance of [Review Board](https://reviews.apache.org/) as well if that is preferred.
-Accumulo operates under the [Commit-Then-Review](https://www.apache.org/foundation/glossary#CommitThenReview) (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 [here](./rb)
+Accumulo operates under the [Commit-Then-Review](https://www.apache.org/foundation/glossary#CommitThenReview) (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 [here](./rb)
### Review Board
diff --git a/contributor/making-release.md b/contributor/making-release.md
index 0a67a274..63e5bb9d 100644
--- a/contributor/making-release.md
+++ b/contributor/making-release.md
@@ -186,7 +186,7 @@ if this is the latest release of Accumulo.
* Update the `accumulo.version` property in `pom.xml` of accumulo-examples
* Run `mvn clean verify` to confirm that nothing breaks
- * Run one of the examples for additinal testing.
+ * Run one of the examples for additional testing.
## References
diff --git a/tour/batch-scanner.md b/tour/batch-scanner.md
index 80c0d113..2d237dc9 100644
--- a/tour/batch-scanner.md
+++ b/tour/batch-scanner.md
@@ -24,7 +24,7 @@ static void exercise(MiniAccumuloCluster mac) throws Exception {
}
```
-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
+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.
1. After the above code, create a BatchScanner with 5 query threads. Similar to a Scanner, use the [createBatchScanner] method.
@@ -34,7 +34,7 @@ don't need the returned keys to be sorted. Follow these steps to efficiently sca
3. We can make the scan more efficient by only bringing back the columns we want. Use [fetchColumn] to get the `villain` family
and `yearsOfService` qualifier.
-4. Finally, use the BatchScanner to calculate the average years of service of 2000 villians.
+4. Finally, use the BatchScanner to calculate the average years of service of 2000 villains.
[BatchScanner]: {% jurl org.apache.accumulo.core.client.BatchScanner %}
[createBatchScanner]: {% jurl org.apache.accumulo.core.client.Connector#createBatchScanner-java.lang.String-org.apache.accumulo.core.security.Authorizations-int- %}
diff --git a/tour/conditional-writer-code.md b/tour/conditional-writer-code.md
index cd9c0c05..e8259764 100644
--- a/tour/conditional-writer-code.md
+++ b/tour/conditional-writer-code.md
@@ -2,7 +2,7 @@
title: Conditional Writer Code
---
-Below is a solution to the excercise.
+Below is a solution to the exercise.
```java
static boolean setAddress(Connector conn, String id, String expectedAddr, String newAddr) {
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services