I have not seen an expert's comment on the previous code I linked to. It
seems (to my young inexperienced eyes) to do an optimal job of providing
realtime access to an index. Anyone else have some experience with this
code?
On 7/12/06, Mark Miller <[EMAIL PROTECTED]> wrote:
http://www.nabble.c
http://www.nabble.com/Fwd%3A-Contribution%3A-LuceneIndexAccessor-t17416.html#a47049
A good implementation for what you need.
- Mark
On 7/12/06, Dominik Bruhn <[EMAIL PROTECTED]> wrote:
Hy,
thanks for your answers.
Uppon creation of the Reader, does Lucene copy the whole Index into RAM?
Or is
Hy,
thanks for your answers.
Uppon creation of the Reader, does Lucene copy the whole Index into RAM? Or is
this cache filled while searching? How can I find out how long it takes to
create the IndexReader? Just time to Create-Call?
Thanks
--
Dominik Bruhn
mailto: [EMAIL PROTECTED]
http://www.d
This is normal behavior. When you open a reader, it takes a snapshot of the
index and uses that snapshot until it is closed, and any updates to the
index in the meantime are invisible to that reader.
You could periodically close and reopen the reader to get the latest data,
it's not necessary to
On Jul 12, 2006, at 12:48 PM, Dominik Bruhn wrote:
Hy,
I got the following situation:
A Servlet runing in Tomcat5. When starting the servlet up it
automatically
creates a IndexReader and stores it in a static variable. For
searching this
variable is used. When adding a document to the inde
