Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of ryan.ramage@gmail.com
 designates 209.85.212.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPmACT5yfghD3eJrQBut8t2iKmg5nyWRv6Hoc5The8PgB7tVCw@mail.gmail.com>
References: 
 <CAO085=Ksrg933NB5KtqRWS8t3XNUQAB+wA9zexKHSCck0s72AA@mail.gmail.com>
	<CAPmACT5yfghD3eJrQBut8t2iKmg5nyWRv6Hoc5The8PgB7tVCw@mail.gmail.com>
Date: Fri, 21 Oct 2011 08:46:51 -0600
Message-ID: 
 <CAL-h1aQLcm6rSoCi9fc3-2dLPO2ci4MkBRiOuAFjVRXggL5v_w@mail.gmail.com>
Subject: Re: data migration / ETL
From: Ryan Ramage <ryan.ramage@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

There is Costco:
https://github.com/harthur/costco

Or Recline:
https://github.com/maxogden/recline

Not sure if those will have enough horsepower for you though.

After reading your question again, it seems to be more about release
management...the versions of software using docs in couch, and
managing the document 'schema'.  In the sql world I have used liqibase
[http://www.liquibase.org/manual/home]. Although I find schema-less
much more relaxing,  I could see some cases where a tool like
liquibase for couchdb would be useful.

Ryan


On Fri, Oct 21, 2011 at 8:20 AM, Sean Copenhaver
<sean.copenhaver@gmail.com> wrote:
> I want to say someone announced a basic utility that safely rolls through
> all docs in the database and performs a task. I think it was a node.js
> command line tool and you provided it a script to run on each document. N=
ot
> positive.
>
> If you have a view that gives you all the documents based on a version
> attribute, then you could roll through all documents in the view for a
> particular version (null, 1.1, etc) perform your ETL process, update the
> version, and store them back. Eventually you should have no documents wit=
h a
> version below the one you are migrating to. Only concern is if you run in=
to
> conflict because someone updates the doc while you are migrating it, but =
I
> suppose in this situation you would follow your normal conflict resolutio=
n
> then migrate the resulting doc.
>
> Anyway just some thoughts off the top of my head. I hope that helps some.
>
> On Tue, Oct 18, 2011 at 9:13 AM, daniel williams
> <daniel.williams@gmail.com>wrote:
>
>> My organization has run into a handful of issues around migration of
>> structures of documents from varying versions of software built upon
>> couchdb. =A0Has anyone in the nets come up with a good solution for
>> structural
>> changes of documents that coincide with major/minor/maintenance releases=
 of
>> software leverage couchdb? =A0perhaps a couch ETL?
>>
>> Thanks.
>>
>> dan
>>
>
>
>
> --
> =93The limits of language are the limits of one's world. =93 - Ludwig von
> Wittgenstein
>
> "Water is fluid, soft and yielding. But water will wear away rock, which =
is
> rigid and cannot yield. As a rule, whatever is fluid, soft and yielding w=
ill
> overcome whatever is rigid and hard. This is another paradox: what is sof=
t
> is strong." - Lao-Tzu
>


--=20
Twitter: @eckoit