[GitHub] [couchdb-documentation] flimzy commented on a change in pull request #510: Attempt to explain partitioning better.

[GitBox <gi...@apache.org>]

flimzy commented on a change in pull request #510: Attempt to explain partitioning better.
URL: https://github.com/apache/couchdb-documentation/pull/510#discussion_r395911136
 
 

 ##########
 File path: src/partitioned-dbs/index.rst
 ##########
 @@ -130,6 +136,33 @@ the query across all ``q`` shards in the database. This mean that you do
 not have to wait for all ``q`` shards to respond, which is both
 efficient and faster.
 
+In other words, you can use partitions to help pre-process views. As another
+example, you may be recording traffic to various websites, and 95% of your
+queries are based around 'what happened in relation to website example.com'.
+By partitioning your database with the key ``example.com:uuid``, and using
+the ``/dbname/_partition/example.com`` query, you are significantly simplifying
+the work the query engine has to do.
+
+When to NOT use partitions?
 
 Review comment:
   ```suggestion
   When to NOT use partitions
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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