lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] Created: (LUCENE-2527) FieldCache.getTermsIndex should cache fasterButMoreRAM=true|false to the same cache key
Date Mon, 05 Jul 2010 12:36:52 GMT
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 - Java
          Issue Type: Bug
    Affects Versions: 4.0
            Reporter: Michael McCandless
            Assignee: Michael McCandless
             Fix For: 4.0


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.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message