UPDATE: I went with method 1, i.e. keeping IndexReader instances open
between requests. Which brings me back to the original questions - is there
any way of quantifying the impact of not closing a particular IndexReader?
Does this depend on # of segments per index, open file count etc?
On Thu, Oc
Hi,
Don't use addDocuments. This method is more made for so called block indexing
(where all documents need to be on a block for block joins). Call addDocument
for each document possibly from many threads. By this Lucene can better handle
multithreading and free memory early. There is really no
- uwe@
Thanks Uwe!
I changed the logic so that my workers only parse input docs into Documents,
and indexWriter does addDocuments() by itself for the chunks of 100 Documents.
Unfortunately, this behaviour reproduces: memory usage slightly increases with
the number of processed documents, and at
Hi,
Thanks for providing us with open source tool. I am interested about the
Macedonian version.
I can't test it in Eclipse, so I want to ask you is this version complete?
Can we use it already in our project?
Are there any problems I should consider when integrating with other
projects?
Thanks
