This forum is in READ-ONLY mode.
You can look around, but if you want to ask a new question, please use Stack Overflow.

Lucene indexing Issue

Questions relating to sfLucenePlugin, sfSearch etc

Lucene indexing Issue

by fortx » Thu Sep 16, 2010 1:04 am


We followed Jobeet instructions for lucene search but here is the situation:
-Lucene index just fine with a table "personas" but using the same configuration with another called "medicosdata" lucene indexes beginning with the second row and it shows the previous one when we search anyone.
Posts: 52
Joined: Fri Jun 25, 2010 8:55 pm
Location: Santo Domingo, Dominican Republic

Re: Lucene indexing Issue

by Maurice99 » Mon Dec 05, 2011 12:54 pm

we are currently intending to implement a document storage / search tool
using Jackrabbit and Lucene. We have been approached by a commercial search
and indexing organisation called ISYS who are suggesting the following
problems with using Lucene. We do have a requirement to store and search
large documents and the total document store will be large too. Any comments
on the following would be greatly appreciated.

1) By default, Lucene only indexes the first 10,000 words from each
document. When increasing this default out-of-memory errors can occur. This
implies that documents, or large sections thereof, are loaded into memory.
ISYS has a very small memory footprint which is not affected by document
size nor number of documents.

2) Lucene appears to be slow at indexing, at least by ISYS' standards.
Published performance benchmarks seem to vary between almost acceptable,
down to very poor. ISYS' file readers are already optimized for the fastest
text extraction possible.

3) The Lucene documentation suggests it can be slow at searching and can get
slower and slower the larger your indexes get. The tipping point is where
the index size exceeds the amount of free memory in your machine. This also
implies that whole indexes, or large portions of them, are loaded into
memory. The bigger the index, the more powerful the machine required. ISYS'
search speed is always proportional to the size of the result set. Index
size does not materially affect search speed and the index is never loaded
into memory. It also appears that Lucene requires hands-on tuning to keep
its search speed acceptable. ISYS' indexes are self-managing and do not
require any maintenance to keep them searchable at full speed.
Junior Member
Posts: 2
Joined: Sat Dec 03, 2011 4:13 pm

Re: Lucene indexing Issue

by atifali » Wed Sep 24, 2014 11:48 am

nice post likei
Junior Member
Posts: 1
Joined: Wed Sep 24, 2014 11:40 am