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 dansantner@me.com designates
 17.158.232.237 as permitted sender)
Content-type: text/plain; charset=iso-8859-1
MIME-version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: BigCouch
From: Dan Santner <dansantner@me.com>
In-reply-to: 
 <CABvT1DE7oMebO_pwXG+WL9SsY=nhZsj9FLAZ1_dEvBZBBw6dMQ@mail.gmail.com>
Date: Thu, 21 Nov 2013 10:58:53 -0600
Content-transfer-encoding: quoted-printable
Message-id: <76BC0123-915C-4746-B314-39FF44B5E9ED@me.com>
References: 
 <CAHdxAHsEaAb_1c9pW6g9usLWo47P52UqUZjUEojdT8N0HU7KVQ@mail.gmail.com>
 <5059112F-CCE8-42CB-8EF4-180CA4CC5592@me.com>
 <CABvT1DE7oMebO_pwXG+WL9SsY=nhZsj9FLAZ1_dEvBZBBw6dMQ@mail.gmail.com>
To: user@couchdb.apache.org

I will gladly test for you guys once you have something :).
On Nov 21, 2013, at 10:52 AM, Robert Newson <rnewson@apache.org> wrote:

> Hi,
>=20
> There has been a protracted lull in the bigcouch merger work but we're
> doing some more at couchhack in December and then a whole lot more in
> Q1, hopefully to completion.
>=20
> We're not yet sure what migration will look like. At worse, it will be
> replication based but we're mindful to do better.
>=20
> 0.4 is stable enough but note that it's 2+ years old from the author's
> (Cloudant's) point of view and is no longer under active development
> or maintenance.
>=20
> For clarity, the merge is emphatically not the bigcouch code base but,
> rather, the code that Cloudant runs in production as of around April.
> Once the merge is done, we can look at porting all the core
> improvements we've made since then.
>=20
> B.
>=20
>=20
>=20
> On 21 November 2013 16:31, Dan Santner <dansantner@me.com> wrote:
>> I use bigcouch in a production system.  In my case it's been pretty =
stable but we don't have massive usage yet.
>>=20
>> It was one of the easiest things for me to setup honestly.  And if =
you don't actually need your own instance running on your own nodes just =
use cloudant which makes the deployment steps go away :).
>>=20
>> Dan.
>> On Nov 21, 2013, at 10:24 AM, Jens Rantil <jens.rantil@gmail.com> =
wrote:
>>=20
>>> Hi,
>>>=20
>>> I think I have a use case that would fit BigCouch quite well. This =
brings
>>> me to three questions:
>>>=20
>>>  - When is the BigCouch merge expected to be released? Maybe I =
should
>>>  focus on getting that one working if it's near in time.
>>>  - If I choose to go with the original BigCouch, will it be easy to
>>>  migrate to CouchDB when the BigCouch merge is done?
>>>  - The BigCouch version is 0.4, but I guess it's production ready?
>>>=20
>>>=20
>>> Cheers,
>>> Jens
>>=20