couchdb-lucene used to be updated via update_notification but this
required couchdb to launch Java which... sucked.
couchdb-lucene 0.5+ runs as a separate daemon and pulls data from
couchdb via _changes calls, and this has been much better.
the externals interface still serializes queries which s
hat this
> could still go through the current _fti URL's (without adding some
> mod_rewrite like magic).
>
> Nils.
>
> Van: Robert Newson [robert.new...@gmail.com]
> Verzonden: dinsdag 27 juli 2010 23:41
> Aan: user@couchdb.apa
Bob,
can you explain more, I should have said update_notification, I have
an external query handler and a update notification for updating the
index. The problem is that the data gets into the database quickly I
perform an external query and the update handler hasn't had time to
work.
I am using
that this
could still go through the current _fti URL's (without adding some mod_rewrite
like magic).
Nils.
Van: Robert Newson [robert.new...@gmail.com]
Verzonden: dinsdag 27 juli 2010 23:41
Aan: user@couchdb.apache.org
Onderwerp: Re: external handlers
reading _changes instead of using the (deprecated?) externals feature
would avoid the problem?
B.
On Tue, Jul 27, 2010 at 10:37 PM, J Chris Anderson wrote:
>
> On Jul 27, 2010, at 2:30 PM, Norman Barker wrote:
>
>> Hi,
>>
>> I have written couchdb-clucene
>> (http://github.com/normanb/couchdb-cl
On Jul 27, 2010, at 2:30 PM, Norman Barker wrote:
> Hi,
>
> I have written couchdb-clucene
> (http://github.com/normanb/couchdb-clucene) and am doing a lot of
> testing with heavy datasets where I am sending a bulk doc request with
> 10 docs at a time, a couple of these every second for a couple
Hi,
I have written couchdb-clucene
(http://github.com/normanb/couchdb-clucene) and am doing a lot of
testing with heavy datasets where I am sending a bulk doc request with
10 docs at a time, a couple of these every second for a couple of
minutes.
Very quickly couchdb backs up and hogs the cpu sin
