I'm pretty new with this, but with my index for a database, I'm using
a Quartz scheduler. Also at the end of the index update, I set my
singleton of IndexSearcher to null. That way the index searcher will
be using the latest information. That bit as well as setting it to
null and not closing it I found searching around on forums. The
reason given for not closing it is to allow searches currently using
the index searches to finish using it.
Anyway, I hope this helps.
Jeremy
On Apr 17, 2006, at 2:53 PM, Marc Dauncey wrote:
Hi everyone,
I'm currently designing a Lucene search system and i'm
considering the indexing side of things.
Just wondered what kind of architecture people have
adopted for indexing - are CHRON jobs sufficient for
high volume drip feed indexing or has anyone
implemented a more sophisticated solution with web
services to index on demand?
And has anyone used Quartz to schedule Lucene index
updates? Sounds like an interesting product in this
context.
Many thanks
Marc Dauncey
___________________________________________________________
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide
with voicemail http://uk.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
