ACCUMULO-3962 Fix minor typos in user manual
Project: http://git-wip-us.apache.org/repos/asf/accumulo/repo Commit: http://git-wip-us.apache.org/repos/asf/accumulo/commit/e4f1df32 Tree: http://git-wip-us.apache.org/repos/asf/accumulo/tree/e4f1df32 Diff: http://git-wip-us.apache.org/repos/asf/accumulo/diff/e4f1df32 Branch: refs/heads/master Commit: e4f1df32712351b252e8a3c128702e4aa8216284 Parents: 5f76160 Author: Christopher Tubbs <ctubb...@apache.org> Authored: Thu Aug 13 12:31:49 2015 -0400 Committer: Christopher Tubbs <ctubb...@apache.org> Committed: Thu Aug 13 12:31:49 2015 -0400 ---------------------------------------------------------------------- docs/src/main/asciidoc/chapters/iterator_design.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/accumulo/blob/e4f1df32/docs/src/main/asciidoc/chapters/iterator_design.txt ---------------------------------------------------------------------- diff --git a/docs/src/main/asciidoc/chapters/iterator_design.txt b/docs/src/main/asciidoc/chapters/iterator_design.txt index 02c9973..b9def10 100644 --- a/docs/src/main/asciidoc/chapters/iterator_design.txt +++ b/docs/src/main/asciidoc/chapters/iterator_design.txt @@ -312,7 +312,7 @@ pair that has the largest timestamp. === Best practices Because of the flexibility that the `SortedKeyValueInterface` provides, it doesn't directly disallow -many implementations which are poor desigin decisions. The following are some common recommendations to +many implementations which are poor design decisions. The following are some common recommendations to follow and pitfalls to avoid in Iterator implementations. ==== Avoid special logic encoded in Ranges @@ -324,7 +324,7 @@ should *never* make assumptions about the current state/context based on the `Ra The common failure condition is referred to as a "re-seek". In the context of a Scan, TabletServers construct the "stack" of Iterators and batch up Key-Value pairs to send back to the client. When a sufficient number of Key-Value -pairs are collected, it is commons for the Iterators to be "torn down" until the client asks for the next batch of +pairs are collected, it is common for the Iterators to be "torn down" until the client asks for the next batch of Key-Value pairs. This is done by the TabletServer to add fairness in ensuring one Scan does not monopolize the available resources. When the client asks for the next batch, the implementation modifies the original Range so that servers know the point to resume the iteration (to avoid returning duplicate Key-Value pairs). Specifically, the new Range is created
