Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: Contribution: CouchDb dump and reload
From: Filippo Fadda <filippo.fadda@programmazione.it>
In-Reply-To: 
 <CAHdjipKGBLH=W=yorVYYvbswnKad3rUxqb9uPaLzBj27qLGdNg@mail.gmail.com>
Date: Fri, 4 Oct 2013 02:28:56 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <46C56CF3-C72A-49E3-AAD1-9A5EF914C74B@programmazione.it>
References: <524DB903.5010405@fiset.ca> <524DBABA.8080903@orgmeta.com>
 <9292ECFF-41C2-498C-A062-5FB6775C8B1F@couchbase.com>
 <CAHdjipKGBLH=W=yorVYYvbswnKad3rUxqb9uPaLzBj27qLGdNg@mail.gmail.com>
To: user@couchdb.apache.org

Is it basically an all_docs + include_docs?

-Filippo

On Oct 3, 2013, at 11:51 PM, Alexander Shorin wrote:

> On Fri, Oct 4, 2013 at 1:28 AM, Jens Alfke <jens@couchbase.com> wrote:
>> On Oct 3, 2013, at 11:43 AM, Vivek Pathak <vpathak@orgmeta.com> =
wrote:
>>=20
>>> Just fyi,  there is couchdb-dump available in
>>> tihttp://code.google.com/p/couchdb-python/
>>=20
>> Looks like these two tools use entirely different data formats. Has =
anyone thought of defining a common format for database dumps?
>=20
> I think it will be hard to define such.
>=20
> Dumping CouchDB data as JSON looks intuitive and requires less
> additional actions for import/export. Having couchdb-python approach
> with multipart format provides lesser footprint, but requires a more
> tricky processing (boundaries, headers). Both solutions may use
> CouchDB API without any additional data conversion.  And both requires
> a lot of disk space, much more than if you just copy database file or
> make a replica of it, unless you xz-zip the output.
>=20
> --
> ,,,^..^,,,