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.
omit 8ba77c3 Add Elixir tests for database partitions
omit c0737c5 Support partitioned queries in Mango
omit d1842ad Optimize offset/limit for partition queries
omit 91732cd Optimize all_docs queries in a single partition
omit a923990 Implement partitioned views
omit a4764e6 Implement `couch_db:get_partition_info/2`
omit 46d42d4 Implement partitioned dbs
add 2b3ac5b Implement partitioned dbs
add fa5cd6e Implement `couch_db:get_partition_info/2`
add e5c77e5 Implement partitioned views
add f0a958b Optimize all_docs queries in a single partition
add 5bd2e9a Optimize offset/limit for partition queries
add 7427a7d Support partitioned queries in Mango
add 0d7b776 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 (8ba77c3)
\
N -- N -- N refs/heads/feature/database-partitions (0d7b776)
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/src/couch_partition.erl | 1 -
1 file changed, 1 deletion(-)
