You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by gi...@git.apache.org on 2017/07/18 06:56:49 UTC

[GitHub] nickva opened a new pull request #689: Replications can reuse http-based endpoints after upgrading to https

nickva opened a new pull request #689:  Replications can reuse http-based endpoints after upgrading to https
URL: https://github.com/apache/couchdb/pull/689
 
 
   Since endpoint URI schema is part of the replication ID generation,
   upgrading from http to an https-based service meant losing all the old
   replication checkpoints.
   
   Allow re-using those checkpoints by introducing an intermediate
   replication ID version. If the current replication checkpoint is not
   found, then re-calculate replication IDs of https:// endpoints to make
   them look like http:// endpoints, and try finding those checkpoints.
   
   This version is called "intermediate" because it doesn't change the
   current default replication id calculation algorithm. Conceptually it
   would fit between 3 and 2, but since version numbers are integers then
   3 was bumped to 4 and this algorithm is now number 3.
   
   Issue #688
   
   <!-- 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. -->
   
   ## Testing recommendations
   
   <!-- Describe how we can test your changes.
        Does it provides any behaviour that the end users
        could notice? -->
   
   ## GitHub issue number
   
   <!-- If this is a significant change, please file a separate issue at:
        https://github.com/apache/couchdb/issues
        and include the number here and in commit message(s) using
        syntax like "Fixes #472" or "Fixes apache/couchdb#472".  -->
   
   ## Related Pull Requests
   
   <!-- If your changes affects multiple components in different
        repositories please put links to those pull requests here.  -->
   
   ## Checklist
   
   - [ ] Code is written and works correctly;
   - [ ] Changes are covered by tests;
   - [ ] Documentation reflects the changes;
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services