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 16249e4 Add Elixir tests for database partitions
omit 94d03ce Support partitioned queries in Mango
omit 3a15e24 Optimize offset/limit for partition queries
omit b4335d1 Optimize all_docs queries in a single partition
omit 0b4106f Implement partitioned views
omit cfab308 Implement `couch_db:get_partition_info/2`
omit d19c05c Implement partitioned dbs
add faabedb Implement partitioned dbs
add 966d168 Implement `couch_db:get_partition_info/2`
add 2e473cb Implement partitioned views
add 6956a3a Optimize all_docs queries in a single partition
add 814cc6c Optimize offset/limit for partition queries
add 2b15afc Support partitioned queries in Mango
add fcd62ed 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 (16249e4)
\
N -- N -- N refs/heads/feature/database-partitions (fcd62ed)
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/fabric/src/fabric_util.erl | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
