The concurrency fix was simple. I had forgotten that QueryParser was
not thread-safe and had allowed multiple threads to access the same
instance concurrently. ApacheBench now confirms that concurrent
searching works as expected.
You couldn't trigger these problems via the Python script, since
Robert Newson robert.new...@... writes:
Everything I have testwise is at http://github.com/rnewson/couchdb-lucene
I understand the reluctance to pull in the Java Virtual Machine just
to use Lucene but, in my experience, there's no other comparable
library for features or performance,
), but it least it has the
potential to do so.
Let us know when you have some numbers of couchdb-clucene versus
couchdb-lucene. (We're mainly a Java shop though, so we're not afraid of
running JVM's.)
Nils.
Van: Norman Barker [norman.bar...@gmail.com
Onderwerp: Re: clucene and couchdb
Nils,
I cut 0.5.2 today which includes the concurrency fix for direct querying.
B.
De informatie vervat in deze e-mail en meegezonden bijlagen is uitsluitend
bedoeld voor gebruik door de geadresseerde en kan vertrouwelijke informatie
bevatten. Openbaarmaking
On Fri, Jun 4, 2010 at 5:49 PM, Robert Newson robert.new...@gmail.comwrote:
Everything I have testwise is at http://github.com/rnewson/couchdb-lucene
I understand the reluctance to pull in the Java Virtual Machine just
to use Lucene but, in my experience, there's no other comparable
library
Itamar,
I posted on clucene, one of the main problems is that Java Lucene
allows storing UserData which CLucene doesn't, this allows the couchdb
seq_num to be stored in the Lucene index keeping it in synch.
Robert, can you expand on the concurrency fix, surely stdin / stdout
is still the bottle
Hi,
I am writing a clucene indexer for CouchDB, I have
update_notifications and _fti as a db handler working. I am using
stdout/stdin for the communication and it is looking good.
Looking at http://wiki.apache.org/couchdb/Full_text_search I see that
the index property in the design document
I am writing a clucene indexer for CouchDB, I have
update_notifications and _fti as a db handler working. I am using
stdout/stdin for the communication and it is looking good.
Looking at http://wiki.apache.org/couchdb/Full_text_search I see that
the index property in the design document
The reason couchdb-lucene requires you to write a javascript function
is that there is no single mapping from a couchdb document to a Lucene
Document that suits everyone.
B.
On Fri, Jun 4, 2010 at 10:31 PM, Norman Barker norman.bar...@gmail.com wrote:
Hi,
I am writing a clucene indexer
Sorry my ignorance about clucene. Ignore me **poof**.
--
David Coallier
Document that suits everyone.
B.
On Fri, Jun 4, 2010 at 10:31 PM, Norman Barker norman.bar...@gmail.com
wrote:
Hi,
I am writing a clucene indexer for CouchDB, I have
update_notifications and _fti as a db handler working. I am using
stdout/stdin for the communication and it is looking good
.
On Fri, Jun 4, 2010 at 10:31 PM, Norman Barker norman.bar...@gmail.com
wrote:
Hi,
I am writing a clucene indexer for CouchDB, I have
update_notifications and _fti as a db handler working. I am using
stdout/stdin for the communication and it is looking good.
Looking at http
12 matches
Mail list logo