<!-- Thank you for your contribution!

     Please file this form by replacing the Markdown comments
     with your text. If a section needs no action - remove it.

     Also remember, that CouchDB uses the Review-Then-Commit (RTC) model
     of code collaboration. Positive feedback is represented +1 from committers
     and negative is a -1. The -1 also means veto, and needs to be addressed
     to proceed. Once there are no objections, the PR can be merged by a
     CouchDB committer.

     See: http://couchdb.apache.org/bylaws.html#decisions for more info. -->

## Overview

<!-- Please give a short brief for the pull request,
     what problem it solves or how it makes things better. -->

The PR is aimed to provide downgrade functionality in case there is need to 
downgrade database which was modified by builds with clustered purge feature. 

After database is modified by builds with clustered purge feature, the disk 
version is bumped to 7. Also, there are two newly introduced trees: 
`PurgeTreeState` and `PurgeSeqTreeState`.

Once downgrade function is called, the disk version is back to the latest 
version of current build. Also, `purge_seq` and `purged_docs` are re-introduced 
again. 

PS: current PR is based on commit `28ba48da5877a5d471253c1b587af7e3b3121fd9` 
which doesn't include clustered purge feature.
## Testing recommendations

<!-- Describe how we can test your changes.
     Does it provides any behaviour that the end users
     could notice? -->
TBD

## Related Issues or Pull Requests

<!-- If your changes affects multiple components in different
     repositories please put links to those issues or pull requests here.  -->
https://github.com/apache/couchdb/pull/1370
https://github.com/apache/couchdb/issues/1352

## Checklist

- [X] Code is written and works correctly;
- [ ] Changes are covered by tests;
- [ ] Documentation reflects the changes;


[ Full content available at: https://github.com/apache/couchdb/pull/1616 ]
This message was relayed via gitbox.apache.org for [email protected]

Reply via email to