If you'd consider using a MemoryIndex for this, I'd recommend also
having a look at nux.xom.pool.FullTextUtil and
nux.xom.pool.FullTextPool, adding smart caching for indexes, queries
and results on top of a MemoryIndex. With some luck this (or some
variant of it) could help speed up your us
Yes, I've found MemoryIndex to be very fast for this
kind of thing. This contribution can be used to
further optimize and shortlist the queries to be run
against the new document sat in MemoryIndex.
___
To help you stay sa
Karl,
Have you considered the MemoryIndex for this sort of thing? I've
thought that it would make for an elegant way to handle this sort of
"agent" or notification service such that new documents get indexed
normally, but also a single document goes into a MemoryIndex and is
matched agai
Hello list,
I wrote a search agent thingy for Lucene. It was built to handle huge
amounts of agents.
Rather than one query per agent to find out if the new document is
interesting or not, agent trigger queries are stored in an index that
is queried with the tokens of a new document.
Sin
