[
https://issues.apache.org/jira/browse/LUCENE-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-2527:
---------------------------------
Fix Version/s: (was: 4.7)
4.8
> 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.8
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
