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 d708bd6  Enforce partition size limits
 discard 68a0557  Use an accumulator when merging revision trees
 discard 91af772  Add Elixir tests for database partitions
 discard 0541a31  Support partitioned queries in Mango
 discard 234a963  Use index names when testing index selection
 discard fe6849f  Optimize offset/limit for partition queries
 discard dc53a3f  Optimize all_docs queries in a single partition
 discard cada5c5  Implement partitioned views
 discard a5cd962  Implement `couch_db:get_partition_info/2`
 discard d964ab5  Implement partitioned dbs
 discard 6adcb18  Implement configurable hash functions
 discard c5569ed  Validate design document options more strictly
 discard 993a85f  Pass the DB record to index validation functions
 discard cea5ea0  Implement `fabric_util:open_cluster_db`
 discard 62a294f  Improve `couch_db:clustered_db` flexibility
 discard 442c302  Add PSE API to store opaque properties
     new 5d219dd  Add PSE API to store opaque properties
     new 24a3698  Improve `couch_db:clustered_db` flexibility
     new 3ff043e  Implement `fabric_util:open_cluster_db`
     new 72eb129  Pass the DB record to index validation functions
     new 7bbe828  Validate design document options more strictly
     new 05678b9  Implement configurable hash functions
     new 25ac408  Implement partitioned dbs
     new 6edb9a5  Implement `couch_db:get_partition_info/2`
     new 3a1dd0a  Implement partitioned views
     new eb1ffcf  Optimize all_docs queries in a single partition
     new dc369e9  Optimize offset/limit for partition queries
     new 47efcbd  Use index names when testing index selection
     new 53d3515  Support partitioned queries in Mango
     new 16e6af4  Add Elixir tests for database partitions
     new d830e0c  Use an accumulator when merging revision trees
     new 567efbd  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   (d708bd6)
            \
             N -- N -- N   refs/heads/feature/database-partition-limits 
(567efbd)

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

Reply via email to