This is an automated email from the ASF dual-hosted git repository.
rnewson pushed a change to branch user-partitioned-dbs-4
in repository https://gitbox.apache.org/repos/asf/couchdb.git.
omit 9e3f4d2 validate new partition arguments
omit 79e204b Select only the shard containing the partition, if specified
omit 842da32 Allow partitioned option in mrviews
omit 60f39de expose partitioned flag in GET /dbname info
omit 172ef10 Enforce partition:id format in doc ids
omit f1ee44c map documents to shards by their partition
new 6b5f7a7 map documents to shards by their partition
new 6d5ce6a Enforce partition:id format in doc ids
new 4067fe9 expose partitioned flag in GET /dbname info
new f7e213b Allow partitioned option in mrviews
new f047050 Select only the shard containing the partition, if specified
new 10b5bd3 validate new partition arguments
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 (9e3f4d2)
\
N -- N -- N refs/heads/user-partitioned-dbs-4 (10b5bd3)
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 6 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/mem3/src/mem3_shards.erl | 4 ++--
src/mem3/src/mem3_util.erl | 26 +++++++++++++-------------
2 files changed, 15 insertions(+), 15 deletions(-)
