Hi,
Thanks a lot for your information.
Regards,
Manjula.
On Fri, Jul 23, 2010 at 12:48 PM, tarun sapra t.sapr...@gmail.com wrote:
You can use HibernateSearch to maintain the synchronization between Lucene
index and Mysql RDBMS.
On Fri, Jul 23, 2010 at 11:16 AM, manjula wijewickrema
You could also look at MemoryIndex or InstantiatedIndex, both in
lucene's contrib area. I think that I was also wondering if you might
gain from using TermDocs or TermVectors or something directly.
--
Ian.
On Tue, Jul 27, 2010 at 9:34 PM, Geir Gullestad Pettersen
gei...@gmail.com wrote:
Hi Grant,
thanks for the ideas. I implemented a personal Collector, which returns
all docID's. In the next step I collect all terms using a customised
FieldSelector. This implementation is about 2 to 3 times faster than my
previous implementation using only a customised FieldSelector.
We recently upgraded from lucene 2.4.0 to lucene 3.0.2. Our load testing
revealed a serious performance drop specific to traversing the list of terms
and their associated documents for a given indexed field. Our code looks
something like this:
for(Term term : terms) {
TermDocs termDocs =
that code has way too much stuff in it for your first application.
Hibernate
is in there and it looks, from the description, like it tries to search your
database.
I'd *strongly* recommend that you don't go there.
Try looking at
Hi,
In addition to text content my documents have tags which can be searched
too. The problem now is that the tags change quite often and every time a
tag gets added or removed I have to call UpdateDocument which is quite slow
when done for hundreds of documents.
Are there any well performing
