couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Kocoloski <>
Subject Re: When will BigCouch be merged into Apache Couchdb?
Date Mon, 02 Apr 2012 15:07:56 GMT
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.


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
> Will there be any compatibility issues?
> Is BigCouch going to be an optional clustering component/plugin piece? 
> -- 
> Sean Copenhaver
> On Monday, April 2, 2012 at 10:32 AM, Adam Kocoloski wrote:
>> On Apr 2, 2012, at 10:28 AM, Mike Kimber wrote:
>>> Can anyone able to provide an ETA as to when BigCouch be merged into Apache Couchdb?
>>> Or if not provide any idea what the migration might be from BigCouch to the merged
code base?
>>> Juts trying to worm out if I should wait for the code merge or move to BigCouch
>>> Thanks
>>> Mike
>> 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,
>> Adam 

View raw message