You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "Jenn Turner (JIRA)" <ji...@apache.org> on 2016/08/22 16:33:20 UTC
[jira] [Closed] (COUCHDB-3074) CouchDB 2.0 Blog Series: Migration
Guide
[ https://issues.apache.org/jira/browse/COUCHDB-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jenn Turner closed COUCHDB-3074.
--------------------------------
Resolution: Delivered
Post was published to the Apache CouchDB blog on August 17. Thank you!
> CouchDB 2.0 Blog Series: Migration Guide
> ----------------------------------------
>
> Key: COUCHDB-3074
> URL: https://issues.apache.org/jira/browse/COUCHDB-3074
> Project: CouchDB
> Issue Type: New JIRA Project
> Reporter: Jenn Turner
> Assignee: Sebastian Rothbucher
> Priority: Minor
>
> This issue is to track progress on a series of blog posts promoting the release of CouchDB 2.0.
> Topic: Migration Guide
> - 99% is the same
> - update_seq is opaque string now
> - changes feed can include duplicates
> - JS apps using /_utils/*.js: copy 1.6 files and put into your apps
> - /_config is not available on the cluster, but there is /_node/<fqdn>/ _config/ for your setup needs, make sure you do it on all nodes
> - test suites:
> - if you are creating and deleting databases in quick succession, start using unique db names (and add cleanup)
> - moving from a single node CouchDb 1.6.x to a distributed cluster using 2.0 features.
> - strategies to change the number of nodes safely (adding nodes and/or removing nodes) while already in production
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)