summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndy Wenk <andywenk@apache.org>2014-03-20 23:52:26 +0100
committerAndy Wenk <andywenk@apache.org>2014-03-20 23:52:26 +0100
commitfb59ccae8d90f6407e5b9d08a302f909778db9b7 (patch)
tree3dc492e865e7e44d92d64610dfea2e3798d0134e
parent3be8c85bde6d4ee513a736cdaf7d7aaf171d825d (diff)
downloadcouchdb-fb59ccae8d90f6407e5b9d08a302f909778db9b7.tar.gz
update documentation
explain better what happens with the view index when documents in a view are being processed
-rw-r--r--share/doc/src/intro/overview.rst7
1 files changed, 4 insertions, 3 deletions
diff --git a/share/doc/src/intro/overview.rst b/share/doc/src/intro/overview.rst
index f94d65647..4e3b72c42 100644
--- a/share/doc/src/intro/overview.rst
+++ b/share/doc/src/intro/overview.rst
@@ -198,9 +198,10 @@ simultaneous client readers, who can read and query the view while the index
is concurrently being refreshed for other clients without causing problems
for the readers.
-As documents are examined, their previous row values are removed from the
-view indexes, if they exist. If the document is selected by a view function,
-the function results are inserted into the view as a new row.
+As documents are processed by the view engine through your 'map' and 'reduce'
+functions, their previous row values are removed from the view indexes, if
+they exist. If the document is selected by a view function, the function results
+are inserted into the view as a new row.
When view index changes are written to disk, the updates are always appended
at the end of the file, serving to both reduce disk head seek times during