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 adam.kocoloski@gmail.com
 designates 209.85.216.180 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: When will BigCouch be merged into Apache Couchdb?
From: Adam Kocoloski <adam.kocoloski@gmail.com>
In-Reply-To: <7E4BDA668B7B4B379AEEA90EF9B10073@gmail.com>
Date: Mon, 2 Apr 2012 11:07:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9FF69765-6C9B-4FA0-B69E-11CFA861876A@gmail.com>
References: <A7D50E04F38FD44D9D914F2ABCA592BF2DE19FE366@BE259.mail.lan>
 <296A426D-FD8A-461C-A2C0-A80A12A087BD@apache.org>
 <7E4BDA668B7B4B379AEEA90EF9B10073@gmail.com>
To: user@couchdb.apache.org

Hi Sean, that's correct, there are API incompatibilities, a few of which =
are frankly inevitable.  My position has always been that for those =
cases we make a breaking change in the CouchDB interface so that at the =
end of the day we have a single interface which can be implemented on a =
single server and in a cluster.

As far as whether BigCouch would be optional or a plugin, my hope is =
that we can build a version of Apache CouchDB which runs really well on =
a single server but can transition naturally to a cluster of machines as =
the need arises.  If BigCouch features are not shipping in the core =
server codebase that becomes much more complicated.

Adam

On Apr 2, 2012, at 10:48 AM, Sean Copenhaver wrote:

> I do have some concerns over this. If I remember correctly there are a =
couple of API incompatibilities. =20
>=20
> Will there be any compatibility issues?
>=20
> Is BigCouch going to be an optional clustering component/plugin piece?=20=

>=20
> --=20
> Sean Copenhaver
>=20
>=20
> On Monday, April 2, 2012 at 10:32 AM, Adam Kocoloski wrote:
>=20
>> On Apr 2, 2012, at 10:28 AM, Mike Kimber wrote:
>>=20
>>> Can anyone able to provide an ETA as to when BigCouch be merged into =
Apache Couchdb?
>>>=20
>>> Or if not provide any idea what the migration might be from BigCouch =
to the merged code base?
>>>=20
>>> Juts trying to worm out if I should wait for the code merge or move =
to BigCouch now.
>>>=20
>>> Thanks
>>>=20
>>> Mike
>>=20
>> Hi Mike, I'm afraid we're still firming up an ETA. I wouldn't =
anticipate any major issues migrating from a BigCouch install to a =
future Apache CouchDB install incorporating the BigCouch feature set. =
Regards,
>>=20
>> Adam=20
>=20