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

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


 discard f0efadb  Enforce partition size limits
 discard f578ac2  Use an accumulator when merging revision trees
 discard b98a7c6  Add Elixir tests for database partitions
 discard fbce2c0  Support partitioned queries in Mango
 discard 1c83f62  Use index names when testing index selection
 discard d6213aa  Optimize offset/limit for partition queries
 discard 7ec5717  Optimize all_docs queries in a single partition
 discard ad6b455  Implement partitioned views
 discard c6befe6  Implement `couch_db:get_partition_info/2`
 discard 0c97d71  Implement partitioned dbs
 discard 01715aa  Implement configurable hash functions
 discard 946b942  Validate design document options more strictly
 discard 71a1057  Pass the DB record to index validation functions
 discard 9819cfa  Implement `fabric_util:open_cluster_db`
 discard ed9c97d  Improve `couch_db:clustered_db` flexibility
 discard f3a2eb2  Add PSE API to store opaque properties
     add 3d6247e  Add PSE API to store opaque properties
     add 8f5d0fd  Improve `couch_db:clustered_db` flexibility
     add ce0fb41  Implement `fabric_util:open_cluster_db`
     add ff77a34  Pass the DB record to index validation functions
     add cb7e72e  Validate design document options more strictly
     add 148e6c3  Implement configurable hash functions
     add 219286f  Implement partitioned dbs
     add c61ca17  Implement `couch_db:get_partition_info/2`
     add dace0ba  Implement partitioned views
     add 92f8726  Optimize all_docs queries in a single partition
     add a2020e3  Optimize offset/limit for partition queries
     add b1c7a8a  Use index names when testing index selection
     add 1eb0a51  Support partitioned queries in Mango
     add b4b86b8  Add Elixir tests for database partitions
     add d5a6870  Use an accumulator when merging revision trees
     add 64bd9fc  Enforce partition size limits

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   (f0efadb)
            \
             N -- N -- N   refs/heads/feature/database-partition-limits 
(64bd9fc)

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.

No new revisions were added by this update.

Summary of changes:
 src/couch/test/couch_db_props_upgrade_tests.erl |  83 ++++++
 test/elixir/test/partition_view_test.exs        | 320 +++++++-----------------
 test/elixir/test/partition_view_update_test.exs |  73 ++++++
 3 files changed, 250 insertions(+), 226 deletions(-)
 create mode 100644 src/couch/test/couch_db_props_upgrade_tests.erl
 create mode 100644 test/elixir/test/partition_view_update_test.exs

Reply via email to