This is an automated email from the ASF dual-hosted git repository.
vatamane pushed a change to branch reshard
in repository https://gitbox.apache.org/repos/asf/couchdb.git.
discard c4632f0 Implement resharding HTTP API
discard b738936 Resharding supervisor and job manager
discard 300a51d Shard splitting job implementation
discard 051aa72 Update internal replicator to replicate to multiple targets
discard bcd44a2 Implement initial shard splitting data copy
discard 0d316be Uneven shard copy handling in mem3 and fabric
discard 8d68e4b Added more info for a mango sort error (#1970)
new 8ef42f7 Merge pull request #1971 from apache/weak-etag-comparison
new d98fd88 Added more info for a mango sort error (#1970)
new 5be849e Uneven shard copy handling in mem3 and fabric
new f70245e Implement initial shard splitting data copy
new f49054d Update internal replicator to replicate to multiple targets
new 74a4170 Shard splitting job implementation
new cc27e02 Resharding supervisor and job manager
new cb89bd0 Implement resharding HTTP API
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 (c4632f0)
\
N -- N -- N refs/heads/reshard (cb89bd0)
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 11633 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:
