You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Uwe Schindler (JIRA)" <ji...@apache.org> on 2013/05/10 01:06:06 UTC
[jira] [Updated] (LUCENE-2527) FieldCache.getTermsIndex should
cache fasterButMoreRAM=true|false to the same cache key
[ https://issues.apache.org/jira/browse/LUCENE-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uwe Schindler updated LUCENE-2527:
----------------------------------
Fix Version/s: (was: 4.3)
4.4
> FieldCache.getTermsIndex should cache fasterButMoreRAM=true|false to the same cache key
> ---------------------------------------------------------------------------------------
>
> Key: LUCENE-2527
> URL: https://issues.apache.org/jira/browse/LUCENE-2527
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/search
> Affects Versions: 4.0-ALPHA
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 4.4
>
>
> When we cutover FieldCache to use shared byte[] blocks, we added the boolean fasterButMoreRAM option, so you could tradeoff time/space.
> It defaults to true.
> The thinking is that an expert user, who wants to use false, could pre-populate FieldCache by loading the field with false, and then later when sorting on that field it'd use that same entry.
> But there's a bug -- when sorting, it then loads a 2nd entry with "true". This is because the Entry.custom in FieldCache participates in equals/hashCode.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org