This is an automated email from the ASF dual-hosted git repository.
vatamane pushed a change to branch shard-split
in repository https://gitbox.apache.org/repos/asf/couchdb.git.
discard e9b94c8 Add calculate_max_n to mem3_util module
discard cfb2f6a Rename top level feature "reshard" to match the new API
endpoint
discard 7eab327 Implement resharding HTTP API
discard 222aaee Update internal replicator to replicate to multiple targets
discard 63b6f2c Implement initial shard splitting data copy
discard 7379d5a Shard splitting job implementation
discard ea387ea Resharding supervisor and job manager
discard 176a9fd Uneven shard copy handling in mem3 and fabric
new 1c8918b Uneven shard copy handling in mem3 and fabric
new 2d2e4e2 Resharding supervisor and job manager
new ee64f61 Shard splitting job implementation
new af83bd0 Implement initial shard splitting data copy
new 4bacfed Update internal replicator to replicate to multiple targets
new cd90863 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 (e9b94c8)
\
N -- N -- N refs/heads/shard-split (cd90863)
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 11619 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:
