Sure, that’s the fallback position. CouchDB’s on-disk format has changed
several times over the years, and each time we teach the code to upgrade old to
new as it encounters them. We will do that for current CouchDB to clustered
CouchDB, the question here is whether we will do the same for BigC
Would replication not solve that problem all by itself?
Robert Samuel Newson wrote:
>
>Good question. We are certainly obliged to ensure couchdb pre-merge
>data upgrades to couchdb post-merge but the bigcouch to couchdb path is
>not something we’ve yet committed to. That said, unless it turns o
Good question. We are certainly obliged to ensure couchdb pre-merge data
upgrades to couchdb post-merge but the bigcouch to couchdb path is not
something we’ve yet committed to. That said, unless it turns out to be
intractable (which seems unlikely) we’ll certainly make an effort to support
t
Hello again,
Just wondering if bigcouch data files will be compatible with future
versions of couchdb now that the projects are merged. Will there be
separate ports for data and shards? Will the directory structure of
bigcouch be used or it is completely new? What would be the recommended
option t
