The cache is currently being stored as a static HashMap on the MLT
object and expired at the discretion of the application code using a
static MLT.flushCache() method. Use of the cache at all is opt-in,
using a non-static MLT.setCache(true) and a new constructor signature
on MLTQuery that includes
What was your approach to handling stale cache entries? Did you flush
it when you opened a new reader?
On Apr 7, 2009, at 2:28 AM, Richard Marr wrote:
Hi all,
I've been exploring MoreLikeThisQuery as part of a recent project and
something that came out of that might be useful to others here
Thanks Mike,
I'll leave it a few days to give people time to respond then start
looking into creating a Jira ticket and a patch.
2009/4/7 Michael McCandless :
> I don't have direct experience with MLT, but this sounds like a great
> improvement, so in answer to (3) I would say "definitely!".
>
>
I don't have direct experience with MLT, but this sounds like a great
improvement, so in answer to (3) I would say "definitely!".
Mike
On Tue, Apr 7, 2009 at 2:28 AM, Richard Marr wrote:
> Hi all,
>
> I've been exploring MoreLikeThisQuery as part of a recent project and
> something that came out
