accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mmil...@apache.org
Subject [accumulo-website] branch master updated: Update iterators.md (#146)
Date Fri, 25 Jan 2019 16:41:24 GMT
This is an automated email from the ASF dual-hosted git repository.

mmiller pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/accumulo-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 0fb74e5  Update iterators.md (#146)
0fb74e5 is described below

commit 0fb74e5df463c927693c905147305f3fc780803c
Author: Jeffrey Zeiberg <jzeiberg@gmail.com>
AuthorDate: Fri Jan 25 11:41:20 2019 -0500

    Update iterators.md (#146)
    
    changed the word 'close' to 'closer'
---
 _docs-2/development/iterators.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_docs-2/development/iterators.md b/_docs-2/development/iterators.md
index 8cbdb71..d27fdde 100644
--- a/_docs-2/development/iterators.md
+++ b/_docs-2/development/iterators.md
@@ -12,7 +12,7 @@ in the iteration, Accumulo Iterators must also support the ability to "move"
(`s
 iteration (the Accumulo table). Accumulo Iterators are designed to be concatenated together,
similar to applying a
 series of transformations to a list of elements. Accumulo Iterators can duplicate their underlying
source to create
 multiple "pointers" over the same underlying data (which is extremely powerful since each
stream is sorted) or they can
-merge multiple Iterators into a single view. In this sense, a collection of Iterators operating
in tandem is close to
+merge multiple Iterators into a single view. In this sense, a collection of Iterators operating
in tandem is closer to
 a tree-structure than a list, but there is always a sense of a flow of Key-Value pairs through
some Iterators. Iterators
 are not designed to act as triggers nor are they designed to operate outside of the purview
of a single table.
 


Mime
View raw message