[
https://issues.apache.org/jira/browse/LUCENE-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914470#action_12914470
]
Ryan McKinley commented on LUCENE-2665:
---------------------------------------
bq. Would the validate method do things like compute the validDocs bit set if
the current caller needs it but the entry didn't compute it the first time?
Yes, since the options you ask for in an EntryCreator are not necessarily part
of the key (and therefor the cached entry), I added the validate method to make
sure the cached value has everything it asked for (like validDocs/values) This
is optional since the application may not want to take the time to do this
check (I think it needs to be synchronized)
bq. maybe we have a Cache doReopen() method, on the Cache?
Ya, something like that...
---------
I'll take a crack at this... hopefully we can break this into a few issues, so
that it stays tractable and has a chance of getting committed soon!
> 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
>
>
> 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]
