You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by va...@apache.org on 2019/03/04 15:33:35 UTC
[couchdb] branch shard-split updated (ba77fb1 -> 73cc65e)
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 ba77fb1 [fixup|fabric_ring] add tests for fabric_ring
discard c76cf52 [fixup|fabric] Fix remove overlapping shards behavior
discard 6ae3ab5 [fixup|tests] comment out continuous_feed_should_work_during_split for now
discard 8d7d47c [fixup|fabric_view] move fabric ring logic to fabric_ring
discard 88faa27 Add tests for shard's split changes feed
discard ca70537 Implement resharding HTTP API
discard ac0f9a1 Update internal replicator to replicate to multiple targets
discard 8e89809 Implement initial shard splitting data copy
discard 71f1898 Shard splitting job implementation
discard 97dc338 Resharding supervisor and job manager
discard 6a4f972 Uneven shard copy handling in mem3 and fabric
new 8d65907 Make PropEr an optional (test) dependency
new 5765a54 Merge pull request #1955 from apache/optional-proper
new 92c004b Warn people to edit both Makefiles. (#1952)
new 5a76ebb Uneven shard copy handling in mem3 and fabric
new 27df6cd Resharding supervisor and job manager
new 96a6077 Shard splitting job implementation
new b26c25b Implement initial shard splitting data copy
new 2c4e953 Update internal replicator to replicate to multiple targets
new 0ee42dc Implement resharding HTTP API
new 1cc61f8 Add tests for shard's split changes feed
new 8f10f1a [fixup|fabric_view] move fabric ring logic to fabric_ring
new b4499da [fixup|tests] comment out continuous_feed_should_work_during_split for now
new 5aa418a [fixup|fabric] Fix remove overlapping shards behavior
new 73cc65e [fixup|fabric_ring] add tests for fabric_ring
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 (ba77fb1)
\
N -- N -- N refs/heads/shard-split (73cc65e)
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 11631 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:
Makefile | 4 ++++
Makefile.win | 6 +++++-
configure | 8 ++++++++
rebar.config.script | 22 +++++++++++++++++++---
4 files changed, 36 insertions(+), 4 deletions(-)