You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by mw...@apache.org on 2017/01/05 18:17:49 UTC
[1/3] accumulo-website git commit: ACCUMULO-4548 Fixed grammar errors
on Accumulo Website
Repository: accumulo-website
Updated Branches:
refs/heads/master 7676fd523 -> 7709d48e3
ACCUMULO-4548 Fixed grammar errors on Accumulo Website
Project: http://git-wip-us.apache.org/repos/asf/accumulo-website/repo
Commit: http://git-wip-us.apache.org/repos/asf/accumulo-website/commit/435ad6e0
Tree: http://git-wip-us.apache.org/repos/asf/accumulo-website/tree/435ad6e0
Diff: http://git-wip-us.apache.org/repos/asf/accumulo-website/diff/435ad6e0
Branch: refs/heads/master
Commit: 435ad6e03c28cb3102389603633a64bed2492226
Parents: cb209b3
Author: Luis Tavarez <ze...@outlook.com>
Authored: Wed Jan 4 12:02:49 2017 -0500
Committer: Luis Tavarez <ze...@outlook.com>
Committed: Wed Jan 4 12:02:49 2017 -0500
----------------------------------------------------------------------
contributor/consensusBuilding.md | 6 ++--
contributor/contrib-projects.md | 2 +-
contributor/git.md | 14 ++++----
contributor/lazyConsensus.md | 2 +-
contributor/source.md | 2 +-
contributor/voting.md | 4 +--
pages/features.md | 62 +++++++++++++++++------------------
pages/get_involved.md | 14 ++++----
8 files changed, 53 insertions(+), 53 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/435ad6e0/contributor/consensusBuilding.md
----------------------------------------------------------------------
diff --git a/contributor/consensusBuilding.md b/contributor/consensusBuilding.md
index 4211854..bd5fec2 100644
--- a/contributor/consensusBuilding.md
+++ b/contributor/consensusBuilding.md
@@ -3,8 +3,8 @@ title: Consensus Building
redirect_from: /governance/consensusBuilding
---
-In some cases there is no obvious path to take, or you might be a new community,
-or a new member of an existing community. In these cases people will often
+In some cases, there is no obvious path to take, or you might be a new community,
+or a new member of an existing community. In these cases, people will often
need to build consensus by making proposals and eliciting responses.
We want to avoid unnecessary discussion and the creation of significant
@@ -47,7 +47,7 @@ that when someone wants to summarise a discussion thread they can mentally
add up the strength of feeling of the community and decide if there is consensus
or not.
-Once there is a clear consensus members of the community can proceed with
+Once there is a clear consensus, members of the community can proceed with
the work under the [lazy consensus][1] model.
[1]: {{ site.baseurl }}/contributor/lazyConsensus
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/435ad6e0/contributor/contrib-projects.md
----------------------------------------------------------------------
diff --git a/contributor/contrib-projects.md b/contributor/contrib-projects.md
index b6bca4c..d097106 100644
--- a/contributor/contrib-projects.md
+++ b/contributor/contrib-projects.md
@@ -4,7 +4,7 @@ redirect_from: /contrib
---
Apache Accumulo is a complex distributed system. In order to minimize that
-complexity for both operators and developers the project maintains contrib
+complexity, for both operators and developers, the project maintains contrib
repositories for instructive applications and code that builds interoperability
between Accumulo and other systems. This helps minimize the set of dependencies
needed when building or installing Accumulo, keeps the build time down, and
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/435ad6e0/contributor/git.md
----------------------------------------------------------------------
diff --git a/contributor/git.md b/contributor/git.md
index 95128cf..a5991a4 100644
--- a/contributor/git.md
+++ b/contributor/git.md
@@ -6,12 +6,12 @@ redirect_from: /git
[Git](https://git-scm.com) is an open source, distributed version control system
which has become very popular in large, complicated software projects due to
its efficient handling of multiple, simultaneously and independently developed
-branches of source code.\
+branches of source code.
## Workflow Background
-Likely the most contested subject matter regarding switching an active team
+The most likely contested subject matter regarding switching an active team
from one SCM tool to another is a shift in the development paradigm.
Some background, the common case, as is present with this team, is that
@@ -250,7 +250,7 @@ commit. See the [Git
manual](https://git-scm.com/book/en/Git-Branching-Basic-Branching-and-Merging)
for more information on merging. When merging a pull-request, it's best to **not**
include a signoff on the commit(s) as it changes the final commit ID in the
-Accumulo repository. This also has the negative of not automatically closing
+Accumulo repository. This also has the negative effect of not automatically closing
the Pull-Request when the changes are made public.
### Feature Branches
@@ -330,7 +330,7 @@ releases, changes which are different in implementation due to API changes, or
any number of other cases. Whatever the actual case is, the developer who made
the first set of changes (you) is the one responsible for performing the merge
through the rest of the active versions. Even when the merge may results in a
-zero-length change in content, this is incredibly important to record as you
+zero-length change in content, this is incredibly important to record, as you
are the one who knows that this zero-length change in content is correct!
## Release Management
@@ -405,11 +405,11 @@ of work necessary in opening multiple INFRA tickets.
## Mirroring
-It should be noted in the INFRA requst that each repository will also need to
+It should be noted in the INFRA request that each repository will also need to
be configured to properly mirror to the [ASF Github](https://github.com/apache)
account to provide the same functionality with current have via the git+svn
-mirror. This should be noted in the INFRA request. Same change needs to be
-applied for the [Apache hosted](https://git.apache.org) mirror'ing.
+mirror. Same change needs to be applied for the [Apache hosted](https://git.apache.org)
+mirror'ing.
## Mailing lists
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/435ad6e0/contributor/lazyConsensus.md
----------------------------------------------------------------------
diff --git a/contributor/lazyConsensus.md b/contributor/lazyConsensus.md
index 367a0f1..a3e9fd4 100644
--- a/contributor/lazyConsensus.md
+++ b/contributor/lazyConsensus.md
@@ -35,7 +35,7 @@ and cares.
Sometimes a member of the community will believe a specific action is the correct
one for the community but are not sure enough to proceed with the work under the
-lazy consensus model. In these circumstances they can state Lazy Consensus is in
+lazy consensus model. In these circumstances, they can state Lazy Consensus is in
operation.
What this means is that they make a proposal and state that they will start
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/435ad6e0/contributor/source.md
----------------------------------------------------------------------
diff --git a/contributor/source.md b/contributor/source.md
index 466f5e2..a6db5e8 100644
--- a/contributor/source.md
+++ b/contributor/source.md
@@ -96,7 +96,7 @@ To check out the code:
#### Running a Build
-Accumulo uses [Apache Maven][maven] to handle source building, testing, and packaging. To build Accumulo you will need to use Maven version 3.0.5 or later.
+Accumulo uses [Apache Maven][maven] to handle source building, testing, and packaging. To build Accumulo, you will need to use Maven version 3.0.5 or later.
You should familiarize yourself with the [Maven Build Lifecycle][lifecycle], as well as the various plugins we use in our [POM][pom], in order to understand how Maven works and how to use the various build options while building Accumulo.
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/435ad6e0/contributor/voting.md
----------------------------------------------------------------------
diff --git a/contributor/voting.md b/contributor/voting.md
index 4ee6437..e499918 100644
--- a/contributor/voting.md
+++ b/contributor/voting.md
@@ -9,10 +9,10 @@ release.
## Preparing for a Vote
-Before calling a vote it is important to ensure that the community is given time to
+Before calling a vote, it is important to ensure that the community is given time to
discuss the upcoming vote. This will be done by posting an email to the list
indicating the intention to call a vote and the options available. By the time a
-vote is called there should already be [consensus in the community][1]. The vote
+vote is called, there should already be [consensus in the community][1]. The vote
itself is, normally, a formality.
## Calling a Vote
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/435ad6e0/pages/features.md
----------------------------------------------------------------------
diff --git a/pages/features.md b/pages/features.md
index 26cbb02..6d27a22 100644
--- a/pages/features.md
+++ b/pages/features.md
@@ -34,7 +34,7 @@ Constraints are written in Java and configurable on a per table basis.
### Sharding
Through the use of specialized iterators, Accumulo can be a parallel sharded
-document store. For example wikipedia could be stored and searched for
+document store. For example, Wikipedia could be stored and searched for
documents containing certain words.
### Large Rows
@@ -52,11 +52,11 @@ internally by Accumulo.
### Volume support
-Accumulo 1.6.0 migrated away from configuration of HDFS by using a single HDFS host and
-directory, to a collection of HDFS URIs (host and path) which allows Accumulo to operate
-over multiple disjoint HDFS instances. This allows Accumulo to scale beyond the limits
-of a single namenode. When used in conjunction with HDFS federation, multiple namenodes
-can share a pool of datanodes.
+Accumulo 1.6.0 migrated the HDFS configuration from a single HDFS host and directory
+to a collection of HDFS URIs (host and path). This allows Accumulo to operate over
+multiple disjoint HDFS instances and scale beyond the limits of a single namenode. When
+used in conjunction with HDFS federation, multiple namenodes can share a pool
+of datanodes.
## Integrity/Availability
@@ -72,7 +72,7 @@ and Zookeeper (see [FATE][FATE]).
A mechanism to ensure that server set times never go backwards, even when time
across the cluster is incorrect. This ensures that updates and deletes are not
lost. If a tablet is served on machine with time a year in the future, then the
-tablet will continue to issue new timestamps a year in the future even when it
+tablet will continue to issue new timestamps a year in the future, even when it
moves to another server. In this case the timestamps preserve ordering, but
lose their meaning. In addition to logical time, Accumulo has master
authoritative time. The master averages the time of all of the tablet servers
@@ -101,7 +101,7 @@ Fault Tolerant Executor. A framework for executing operations in a fault
tolerant manner. In the previous release, if the master process died in the
middle of creating a table it could leave the system in an inconsistent state.
With this new framework, if the master dies in the middle of create table it
-will continue on restart. Also the client requesting the create table operation
+will continue on restart. Also, the client requesting the create table operation
will never know anything happened. The framework serializes work in Zookeeper
before attempting to do the work. Clients start a FATE transaction, seed it
with work, and then wait for it to finish. Most table operations are executed
@@ -123,12 +123,12 @@ Scans will not see data inserted into a row after the scan of that row begins.
If consecutive keys have identical portions (row, colf, colq, or colvis), there
is a flag to indicate that a portion is the same as that of the previous key.
This is applied when keys are stored on disk and when transferred over the
-network. Starting with 1.5, prefix erasure is supported. When its cost
+network. Starting with 1.5, prefix erasure is supported. When it is cost
effective, prefixes repeated in subsequent key fields are not repeated.
### Native In-Memory Map
-By default data written is stored outside of Java managed memory into a C++ STL
+By default, data written is stored outside of Java managed memory into a C++ STL
map of maps. It maps rows to columns to values. This hierarchical structure
improves performance of inserting a mutation with multiple column values in a
single row. A custom STL allocator is used to avoid the global malloc lock and
@@ -149,8 +149,8 @@ indexes and data. Caching can be turned on and off for individual tables.
### Multi-level RFile Index
-RFiles store an index of the last key in each block. For large files the index
-can become quite large. When the index is large a lot of memory is consumed and
+RFiles store an index of the last key in each block. For large files, the index
+can become quite large. When the index is large, a lot of memory is consumed and
files take a long time to open. To avoid this problem, RFiles have a
multi-level index tree. Index blocks can point to other index blocks or data
blocks. The entire index never has to be resident, even when the file is
@@ -160,11 +160,11 @@ per table basis.
### Binary search in RFile blocks
-RFile uses its index to locate a block of key values. Once it reaches a block
-it performs a linear scan to find a key on interest. Accumulo will generate
-indexes of cached blocks in an adaptive manner. Accumulo indexes the blocks
-that are read most frequently. When a block is read a few times, a small index
-is generated. As a block is read more, larger indexes are generated making
+RFile uses its index to locate a block of key values. Once it reaches a block,
+it performs a linear scan to find a key of interest. Accumulo will generate
+indexes of cached blocks in an adaptive manner. Accumulo indexes the most
+frequently read blocks. When a block is read a few times, a small index
+is generated. As a block is read more, larger indexes are generated, making
future seeks faster. This strategy allows Accumulo to dynamically respond to
read patterns without precomputing block indexes when RFiles are written.
@@ -186,8 +186,8 @@ instance more closely.
Using the Mini Accumulo Cluster in unit and integration tests is a great way for
developers to test their applications against Accumulo in an environment that is
-much closer to physical deployments than Mock Accumulo provided. Accumulo 1.6.0 also
-introduced a [maven-accumulo-plugin][M-A-P] which
+much closer to physical deployments than a Mock Accumulo environment.
+Accumulo 1.6.0 also introduced a [maven-accumulo-plugin][M-A-P] which
can be used to start a Mini Accumulo Cluster instance as a part of the Maven
lifecycle that your application tests can use.
@@ -241,7 +241,7 @@ Instead of writing individual mutations to Accumulo, entire files of sorted key
value pairs can be imported. These files are moved into the Accumulo directory
and referenced by Accumulo. This feature is useful for ingesting a large amount
of data. This method of ingest usually offers higher throughput at the cost of
-higher latency for data availability for scans. Usually the data is sorted
+higher latency for data availability for scans. Usually, the data is sorted
using map reduce and then bulk imported. This method of ingest also allows for
flexibility in resource allocation. The nodes running map reduce to sort data
could be different from the Accumulo nodes.
@@ -262,7 +262,7 @@ available to other languages like Python, Ruby, C++, etc.
In version 1.6.0, Accumulo introduced [ConditionalMutations][7]
which allow users to perform efficient, atomic read-modify-write operations on rows. Conditions can
-be defined using on equality checks of the values in a column or the absence of a column. For more
+be defined using equality checks of the values in a column or the absence of a column. For more
information on using this feature, users can reference the Javadoc for [ConditionalMutation][CMUT] and
[ConditionalWriter][CWRI].
@@ -314,7 +314,7 @@ can be used to optimize the data that compactions will write.
### Monitor page
-A simple web server provides basic information about the system health and
+A simple web server that provides basic information about the system health and
performance. It displays table sizes, ingest and query statistics, server
load, and last-update information. It also allows the user to view recent
diagnostic logs and traces.
@@ -349,7 +349,7 @@ Groups columns within a single file. There is a default locality group so that
not all columns need be specified. The locality groups can be restructured
while the table is online and the changes will take effect on the next
compaction. A tablet can have files with different locality group
-configurations. In this case scans may be suboptimal, but correct, until
+configurations. In this case, scans may be suboptimal, but correct until
compactions rewrite all files. After reconfiguring locality groups, a user can
force a table to compact in order to write all data into the new locality
groups. Alternatively, the change could be allowed to happen over time as
@@ -367,7 +367,7 @@ are considered for compaction. This is done until there are no files to merge.
When a max number of files per tablet is reached, minor compactions will merge
data from the in-memory map with the smallest file instead of creating new
-files. This throttles ingest. In previous releases new files were just created
+files. This throttles ingest. In previous releases, new files were just created
even if major compactions were falling behind and the number of tablets per file
was growing. Without this feature, ingest performance can roughly continue at a
constant rate, even as scan performance decreases because tablets have too many
@@ -376,15 +376,15 @@ files.
### Loading jars using VFS
User written iterators are a useful way to manipulate data in data in Accumulo.
-Before 1.5., users had to copy their iterators to each tablet server. Starting
-with 1.5 Accumulo can load iterators from HDFS using Apache commons VFS.
+Before 1.5, users had to copy their iterators to each tablet server. Starting
+with 1.5, Accumulo can load iterators from HDFS using Apache commons VFS.
### Encryption
Still a work in progress, Accumulo 1.6.0 introduced encryption at rest (RFiles
-and WriteAheadLogs) and wire encryption (Thrift over SSL) to provide enhance the
-level of security that Accumulo provides. It is still a work in progress because
-the intermediate files created by Accumulo when recovering from a TabletServer
+and WriteAheadLogs) and wire encryption (Thrift over SSL) to enhance the level
+of security that Accumulo provides. It is still a work in progress because the
+intermediate files created by Accumulo when recovering from a TabletServer
failure are not encrypted.
## On-demand Data Management
@@ -415,7 +415,7 @@ tablets can be merged.
Allows users to quickly create a new table that references an existing table's
data and copies its configuration. A cloned table and its source table can be
mutated independently. Testing was the motivating reason behind this new
-feature. For example to test a new filtering iterator, clone the table, add the
+feature. For example, to test a new filtering iterator, clone the table, add the
filter to the clone, and force a major compaction.
### Import/Export Table
@@ -457,7 +457,7 @@ The following screenshot shows the monitor master page. This page gives informa
</div>
</div>
-The data generated by the continuous ingest test suite looks like the following. The data is random, but forms many giant linked list. Each ingest client continually generates linked list containing 25 million nodes. In the shell session below a few scans are issued to start following the linked list that the first node in the table is part of.
+The data generated by the continuous ingest test suite looks like the following. The data is random, but forms many giant linked list. Each ingest client continually generates linked list containing 25 million nodes. In the shell session below, a few scans are issued to start following the linked list that the first node in the table is part of.
root@test15 ci> scan
000000000135fbbe 074c:569c [] 2db1de18-cd37-407d-b060-481a0a214c90:000000002b2bcfe1:2e15cb9f62fd22ab:fe6f84c7
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/435ad6e0/pages/get_involved.md
----------------------------------------------------------------------
diff --git a/pages/get_involved.md b/pages/get_involved.md
index e8df1e8..7ebd426 100644
--- a/pages/get_involved.md
+++ b/pages/get_involved.md
@@ -4,8 +4,8 @@ permalink: /get_involved/
---
You don't need to be a software developer to contribute to
-Apache Accumulo. To be successful this project
-requires a huge range of different skills, levels of involvement and degrees of
+Apache Accumulo. To be successful, this project
+requires a huge range of different skills, levels of involvement, and degrees of
technical expertise. So, if you want to get involved in Apache Accumulo, there
is almost certainly a role for you.
@@ -23,7 +23,7 @@ We are looking for people to:
- translate to different languages
- anything you can see that needs doing
-All of these contributions help to keep a project active and strengthen
+All of these contributions help to keep the project active and strengthen
the community. The project team and the broader community will
therefore welcome and encourage participation, and attempt to make it
as easy as possible for people to get involved.
@@ -57,7 +57,7 @@ The most important thing about engaging with any Apache project is that everyone
is equal. All people with an opinion are entitled to express that opinion and, where
appropriate, have it considered by the community.
-To some the idea of having to establish consensus in a large and distributed team
+To some, the idea of having to establish consensus in a large and distributed team
sounds inefficient and frustrating. Don't despair though, The Apache Way has a
set of simple processes to ensure things proceed at a good pace.
@@ -68,17 +68,17 @@ Most of the time we work with the consensus building techniques documented below
### Lazy Consensus
[Lazy consensus][7] is the first, and possibly the most important, consensus building
-tool we have. Essentially lazy consensus means that you don't need to get explicit
+tool we have. Essentially, lazy consensus means that you don't need to get explicit
approval to proceed, but you need to be prepared to listen if someone objects.
### Consensus Building
-Sometimes lazy consensus is not appropriate. In such cases it is necessary to
+Sometimes, lazy consensus is not appropriate. In such cases, it is necessary to
make a proposal to the mailing list and discuss options. There are mechanisms
for quickly showing your support or otherwise for a proposal and
[building consensus][8] amongst the community.
-Once there is a consensus people can proceed with the work under the [lazy
+Once there is a consensus, people can proceed with the work under the [lazy
consensus][9] model.
### Voting
[2/3] accumulo-website git commit: ACCUMULO-4548 Changed a word in
the documentation
Posted by mw...@apache.org.
ACCUMULO-4548 Changed a word in the documentation
Project: http://git-wip-us.apache.org/repos/asf/accumulo-website/repo
Commit: http://git-wip-us.apache.org/repos/asf/accumulo-website/commit/e0b8827d
Tree: http://git-wip-us.apache.org/repos/asf/accumulo-website/tree/e0b8827d
Diff: http://git-wip-us.apache.org/repos/asf/accumulo-website/diff/e0b8827d
Branch: refs/heads/master
Commit: e0b8827dac8ddad37d460b8cd441f92a55523256
Parents: 435ad6e
Author: Luis Tavarez <ze...@outlook.com>
Authored: Wed Jan 4 17:09:41 2017 -0500
Committer: Luis Tavarez <ze...@outlook.com>
Committed: Wed Jan 4 17:09:41 2017 -0500
----------------------------------------------------------------------
pages/features.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/e0b8827d/pages/features.md
----------------------------------------------------------------------
diff --git a/pages/features.md b/pages/features.md
index 6d27a22..df49e7c 100644
--- a/pages/features.md
+++ b/pages/features.md
@@ -52,7 +52,7 @@ internally by Accumulo.
### Volume support
-Accumulo 1.6.0 migrated the HDFS configuration from a single HDFS host and directory
+Accumulo 1.6.0 migrated its HDFS configuration from a single HDFS host and directory
to a collection of HDFS URIs (host and path). This allows Accumulo to operate over
multiple disjoint HDFS instances and scale beyond the limits of a single namenode. When
used in conjunction with HDFS federation, multiple namenodes can share a pool
[3/3] accumulo-website git commit: Merge remote-tracking branch
'lstav/master'
Posted by mw...@apache.org.
Merge remote-tracking branch 'lstav/master'
Project: http://git-wip-us.apache.org/repos/asf/accumulo-website/repo
Commit: http://git-wip-us.apache.org/repos/asf/accumulo-website/commit/7709d48e
Tree: http://git-wip-us.apache.org/repos/asf/accumulo-website/tree/7709d48e
Diff: http://git-wip-us.apache.org/repos/asf/accumulo-website/diff/7709d48e
Branch: refs/heads/master
Commit: 7709d48e321e4becc6e1ebc558be50bc8f7bef91
Parents: 7676fd5 e0b8827
Author: Mike Walch <mw...@apache.org>
Authored: Thu Jan 5 13:12:09 2017 -0500
Committer: Mike Walch <mw...@apache.org>
Committed: Thu Jan 5 13:12:09 2017 -0500
----------------------------------------------------------------------
contributor/consensusBuilding.md | 6 ++--
contributor/contrib-projects.md | 2 +-
contributor/git.md | 14 ++++----
contributor/lazyConsensus.md | 2 +-
contributor/source.md | 2 +-
contributor/voting.md | 4 +--
pages/features.md | 62 +++++++++++++++++------------------
pages/get_involved.md | 14 ++++----
8 files changed, 53 insertions(+), 53 deletions(-)
----------------------------------------------------------------------