Your best bet is to use a searcher manager to manage the searcher instance,
and only refresh the manager if writes are committed. This way the same
searcher instances can be shared by multiple threads.
For the paging, if you want to have a guaranteed consistent view, you have
to keep around the se
I've this scenario in a web application:
1. many users query a Lucene index concurrently (obvious)
2. one user can make several queries (she may have different browser
windows open)
3. all those queries need to have a consistent paging behavior (next,
previous buttons)
4. The index can be updated
Hi,
I am using lucene 4.8. I already have an index. I want to use the
Free text suggester feature when a user queries the index. I am not sure
how to start with this. A sample code snippet or a pointer to one would be
really helpful.
Thanks,
Parnab
Hi,
I was able to finally figure this out.
Lucene's Benchmark utility has some default parsers for TREC datasets.
I noticed while parsing it was not parsing the title correctly for my
dataset, eventually setting it to null.
Therefore it was not getting indexed even though I was asking it to.
I wo
Hi,
Thank you for the answers. At the end I calculated the Topic Frequency
using Java, getting the text, broken into tokens and calculating from
there. It turns out to be around 6 times faster in my case (using cache).
Only the document frequency I keep calculating using Lucene.
Regards,
Bian
