Someone define these Lucene problems? (Assuming you mean couchdb-lucene, of course).
On 10 December 2012 07:52, Andrey Kuprianov <[email protected]> wrote: > No, but it will break Lucene.... Badly... To the point that cleaning up > doesn't help. Although, we're still on Lucene 3.5.x. Hopefully, this > problem doesnt exist on 3.6.x. > > > On Mon, Dec 10, 2012 at 3:45 PM, Paul Davis > <[email protected]>wrote: > >> Well, Lucene probably can't handle it, but Lucene doesn't break the .couch >> file to be sure. >> >> >> On Mon, Dec 10, 2012 at 1:29 AM, Andrey Kuprianov < >> [email protected]> wrote: >> >> > Has problems with Lucene, if you are using it. Do replication, if you >> can. >> > Safer this way. >> > >> > >> > On Mon, Dec 10, 2012 at 3:28 PM, Paul Davis <[email protected] >> > >wrote: >> > >> > > Should be fine. >> > > >> > > >> > > On Mon, Dec 10, 2012 at 1:14 AM, Michael Parker >> > > <[email protected]>wrote: >> > > >> > > > Hi all, >> > > > >> > > > If I have a database that is performing create/update/delete >> operations >> > > on >> > > > documents, and I use cp to copy its .couch file on an ext3 >> filesystem, >> > > will >> > > > my copy be corrupted or have any inconsistencies? Looking at how the >> > > .couch >> > > > file is always increasing in size, and given the whole revision >> system >> > > > employed by CouchDB, I'm thinking that it employs some append-only >> > > logging >> > > > -- so maybe yes? >> > > > >> > > > Thanks, >> > > > Mike >> > > > >> > > >> > >>
