[couchdb] branch prototype/fdb-layer-view-cleanup updated (a1a06f3 -> 7dcc031)

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davisp pushed a change to branch prototype/fdb-layer-view-cleanup
in repository https://gitbox.apache.org/repos/asf/couchdb.git.


    omit a1a06f3  Implement couch_views_cleanup_test.erl
    omit e5575b7  Remove failed view jobs
    omit 06bf88e  Remove jobs on index cleanup
    omit 8c2e22f  Optionally cleanup stale indices automatically
    omit feebc92  Implement _view_cleanup for FoundationDB
    omit 9e78fd9  Implement couch_views:cleanup_indices/2
    omit 0744a39  Extend fabric2_index callbacks for index cleanup
     add 8b0d1a5  Extend fabric2_index callbacks for index cleanup
     add b21feb6  Implement couch_views:cleanup_indices/2
     add b072a62  Implement _view_cleanup for FoundationDB
     add 63c0eb8  Optionally cleanup stale indices automatically
     add bbdc845  Remove jobs on index cleanup
     add ab7385d  Remove failed view jobs
     add 7dcc031  Implement couch_views_cleanup_test.erl

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   (a1a06f3)
            \
             N -- N -- N   refs/heads/prototype/fdb-layer-view-cleanup (7dcc031)

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/fabric2_index.erl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)