[couchdb] branch feature/database-partitions updated (8cd68be -> 91af772)

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davisp pushed a change to branch feature/database-partitions
in repository https://gitbox.apache.org/repos/asf/couchdb.git.


 discard 8cd68be  Add Elixir tests for database partitions
 discard 43cf384  Support partitioned queries in Mango
 discard 3cac240  Use index names when testing index selection
 discard 095392a  Optimize offset/limit for partition queries
 discard 23ab71a  Optimize all_docs queries in a single partition
 discard 08a087a  Implement partitioned views
 discard dfa98b4  Implement `couch_db:get_partition_info/2`
 discard ebd9211  Implement partitioned dbs
 discard 4355825  Implement configurable hash functions
 discard 79b90f5  Validate design document options more strictly
 discard 9c48da4  Pass the DB record to index validation functions
 discard 9872652  Implement `fabric_util:open_cluster_db`
 discard e9024bf  Improve `couch_db:clustered_db` flexibility
 discard fae1207  Add PSE API to store opaque properties
     new 0f833fd  Fix timeout in chttpd_purge_tests
     new 442c302  Add PSE API to store opaque properties
     new 62a294f  Improve `couch_db:clustered_db` flexibility
     new cea5ea0  Implement `fabric_util:open_cluster_db`
     new 993a85f  Pass the DB record to index validation functions
     new c5569ed  Validate design document options more strictly
     new 6adcb18  Implement configurable hash functions
     new d964ab5  Implement partitioned dbs
     new a5cd962  Implement `couch_db:get_partition_info/2`
     new cada5c5  Implement partitioned views
     new dc53a3f  Optimize all_docs queries in a single partition
     new fe6849f  Optimize offset/limit for partition queries
     new 234a963  Use index names when testing index selection
     new 0541a31  Support partitioned queries in Mango
     new 91af772  Add Elixir tests for database partitions

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (8cd68be)
            \
             N -- N -- N   refs/heads/feature/database-partitions (91af772)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 11546 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 src/chttpd/test/chttpd_purge_tests.erl | 36 +++++++++++++++++++++++-----------
 1 file changed, 25 insertions(+), 11 deletions(-)