Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0712E109A4 for ; Mon, 22 Jul 2013 10:58:36 +0000 (UTC) Received: (qmail 61711 invoked by uid 500); 22 Jul 2013 10:58:34 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 61220 invoked by uid 500); 22 Jul 2013 10:58:29 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 60527 invoked by uid 99); 22 Jul 2013 10:58:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jul 2013 10:58:27 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of zrao@qti.qualcomm.com designates 65.197.215.72 as permitted sender) Received: from [65.197.215.72] (HELO sabertooth01.qualcomm.com) (65.197.215.72) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Jul 2013 10:58:21 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1374490700; x=1406026700; h=from:to:subject:date:message-id:mime-version; bh=TSd87996hnnbDaBqMgUht/tROk8IVnP5DhWa+CqbITk=; b=usKH4cDPDgLN7A0oX+9vEQS8bQRkjKr2rnSYSZ+Tq9gNg9S22jwusvn4 drrHmvbsv4qgyC0B06ti4HVwO06MEUXjv6EDgeBUAieJwkcaiOLnrfFwg MLznl+0pCdZX07rAhIb5mFuy2rk6BhFi8FtD1YVB31Uyb9bOLFO2LbIzq A=; X-IronPort-AV: E=Sophos;i="4.89,718,1367996400"; d="scan'208,217";a="47859210" Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth01.qualcomm.com with ESMTP; 22 Jul 2013 03:57:59 -0700 X-IronPort-AV: E=Sophos;i="4.89,718,1367996400"; d="scan'208,217";a="508477608" Received: from nasanexhc15.na.qualcomm.com ([129.46.52.215]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 22 Jul 2013 03:57:59 -0700 Received: from NASANEXD02C.na.qualcomm.com ([169.254.6.181]) by nasanexhc15.na.qualcomm.com ([129.46.52.215]) with mapi id 14.02.0318.004; Mon, 22 Jul 2013 03:57:59 -0700 From: "Rao, Zhiqing" To: "user@couchdb.apache.org" Subject: Is it fine to replicate databases from couchdb v1.1.1 to v1.3.0 / v1.3.1? Thread-Topic: Is it fine to replicate databases from couchdb v1.1.1 to v1.3.0 / v1.3.1? Thread-Index: Ac6GyXlV2Lq2iECjRcGM6eyTHSLeKg== Date: Mon, 22 Jul 2013 10:57:58 +0000 Message-ID: <3AB2EC8A0B22CB42B8DD61B5198DA2AF901792@NASANEXD02C.na.qualcomm.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.30.39.5] Content-Type: multipart/alternative; boundary="_000_3AB2EC8A0B22CB42B8DD61B5198DA2AF901792NASANEXD02Cnaqual_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_3AB2EC8A0B22CB42B8DD61B5198DA2AF901792NASANEXD02Cnaqual_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, We have some old databases that with couchDB v1.1.1 , and now we want to ad= d another server with the new version of couchdb, probably v1.3.0 or v1.3.1= . I have replicated some of the databases and the documents within them looks= fine. However, I am not quite confident that it has no side effects or kno= wn issues with this kind of none matching versions replication. Is there anybody have tried this kind of replication before and it works qu= ite well? Thanks, Zhiqing --_000_3AB2EC8A0B22CB42B8DD61B5198DA2AF901792NASANEXD02Cnaqual_--