[
https://issues.apache.org/jira/browse/LUCENE-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741480#action_12741480
]
Hoss Man commented on LUCENE-1798:
----------------------------------
https://issues.apache.org/jira/browse/LUCENE-1749?focusedCommentId=12741479#action_12741479
{quote}
FieldCacheImpl.Cache.get could use the FieldCacheSanityChecker to inspect
itself immediately after calling createValue, and could even test if any of the
Insanity instances returned are related to the current call (by comparing the
CacheEntry with the Entry it's using) ... it could even log a useful stack
trace since the sanity check would be happening in the same call stack as at
least one of the CacheEntries in the Insanity object.
{quote}
> FieldCacheSanityChecker called directly by FieldCache.get*
> ----------------------------------------------------------
>
> Key: LUCENE-1798
> URL: https://issues.apache.org/jira/browse/LUCENE-1798
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: Hoss Man
>
> 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 object.
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
