[
https://issues.apache.org/jira/browse/LUCENE-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated LUCENE-2665:
----------------------------------
Attachment: LUCENE-2665-FieldCacheOverhaul.patch
This patch takes the work from LUCENE-2649 and applies it to a more general
ReaderCache.
The *BIG* changes with this is that it does not have a global notion of
'insane' cache behavior.
To allow EntryCreators to check for insanity, I added a callback where you
could check other things:
{code:java}
public boolean checkCacheAnomaliesAfterPut(ReaderCache cache, EntryKey key, T
newValue )
{code}
I think the one general thing we should check for is the same Key used in any
ReaderCache within the same Directory...
The other thing that was removed is the CacheEntry stuff.
> Rework FieldCache to be more flexible/general
> ---------------------------------------------
>
> Key: LUCENE-2665
> URL: https://issues.apache.org/jira/browse/LUCENE-2665
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: Ryan McKinley
> Attachments: LUCENE-2665-FieldCacheOverhaul.patch,
> LUCENE-2665-FieldCacheOverhaul.patch
>
>
> The existing FieldCache implementation is very rigid and does not allow much
> flexibility. In trying to implement simple features, it points to much
> larger structural problems.
> This patch aims to take a fresh approach to how we work with 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: [email protected]
For additional commands, e-mail: [email protected]
