lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-1798) FieldCacheSanityChecker called directly by FieldCache.get*
Date Mon, 24 Aug 2009 09:27:59 GMT


Michael McCandless commented on LUCENE-1798:

bq. Why not just a single call after the val has been created and log if any of the Insanity
objects contain the new val?

I was worried about over-printing of previously created insanities, but you're right: since
the new entry was just created, there's no way any insanity involving this entry would have
been printed before (duh!).  So I'll simplify it...

> FieldCacheSanityChecker called directly by FieldCache.get*
> ----------------------------------------------------------
>                 Key: LUCENE-1798
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>            Reporter: Hoss Man
>            Assignee: Michael McCandless
>             Fix For: 2.9
>         Attachments: LUCENE-1798.patch
> As suggested by McCandless in LUCENE-1749, we can make FieldCacheImpl a client of the
FieldCacheSanityChecker and have it sanity check itself each time it creates a new cache entry,
and log a warning if it thinks there is a problem.  (although we'd probably only want to do
this if the caller has set some sort of infoStream/warningStream type property on the FieldCache

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message