couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Newson <rnew...@apache.org>
Subject Re: The BigCouch merge, CouchDB 2.0, 3.0 and later
Date Sun, 31 Mar 2013 20:26:08 GMT
That said, it would be great to reap state that we will never need again, it just mustn't happen
before every replica has seen it. 

Sent from my iPhone

On 31 Mar 2013, at 20:55, Jan Lehnardt <jan@apache.org> wrote:

> 
> On Mar 31, 2013, at 21:48 , Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
> 
>> On Sun, Mar 31, 2013 at 9:42 PM, Jan Lehnardt <jan@apache.org> wrote:
>>> We will be collecting things here:
>>> 
>>> https://issues.apache.org/jira/browse/COUCHDB-1756
>>> 
>>> There is an (incomplete) list of differences down on:
>>> 
>>> http://bigcouch.cloudant.com/api
>>> 
>>> Robert & Paul et.al will help getting the COUCHDB-1765 filled out for
>>> discussion & details.
>> 
>> Thanks, that looks very useful (and takes away pretty much all of my
>> qualms). Will _purge be going away entirely?
> 
> I’d like to keep it, but the current version isn’t cluster-able (Robert
> says), so we’d need a new way of implementing this.
> 
> When we discussed this we differentiated two different points in time:
> 
>  1. When is BigCouch ready to merge into Apache CouchDB?
>  2. When do we ship it?
> 
> I’d say 1. can live without _purge as long as we get it back for 2. or 
> we decide as a group that we don’t want it anymore, and we can discuss
> that as part of COUCHDB-1765 or sub-issues.
> 
> There are a few more features like this (vhosts e.g.) that need to go
> through a similar phase. We mainly made the distinction of requirements
> so make sure we get the BigCouch merge work in as soon as possible, so
> the current work gets stale again.
> 
> Jan
> --
> 

Mime
View raw message