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

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

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

 ##########
 File path: src/partitioned-dbs/index.rst
 ##########
 @@ -105,14 +105,20 @@ sensor readings from an IoT field monitoring service. In this particular
 use case, it's quite logical to group all documents by their ``sensor_id``
 field. In this case, we would call the ``sensor_id`` the partition.
 
+A partition offers two benefits. Firstly, it allows you to simplify the
+workload on the query engine, by allowing the engine to only query shards
 
 Review comment:
   I'm not sure "simplify the workload" is clearer here. What it's doing is allowing the user to group data in a way that is understood _a priori_, a.k.a. ahead of time. Since most searches (theoretically) are being done only within one given partition, queries are _optimised_ by only having to run within any one given partition at a time.

----------------------------------------------------------------
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