lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Updated] (LUCENE-2483) When loading FieldCache terms index, make terms data optional
Date Thu, 09 May 2013 23:06:07 GMT


Uwe Schindler updated LUCENE-2483:

    Fix Version/s:     (was: 4.3)
> When loading FieldCache terms index, make terms data optional
> -------------------------------------------------------------
>                 Key: LUCENE-2483
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/search
>            Reporter: Michael McCandless
>             Fix For: 4.4
> Spinoff of LUCENE-2380.
> Now, when you load the terms index (FC.getTermsIndex), it loads two
> arrays, ord (maps docID -> ord) and lookup (maps ord -> term).
> But sometimes you don't need the lookup map (and, it's often very
> costly in RAM usage, much moreso than the ord map).
> EG if your index is a single segment, and your app doesn't need the
> values (LUCENE-2335).
> Or, if you use a sort comparator that resolves ord -> term and v/v (eg
> using terms dict).
> So we should make it optional...
> Also, similarly, we could merge getTerms/getTermsIndex.  It's
> dangerous today if you load terms and then termsIndex because you're
> wasting tons of RAM; it'd be nicer if we could have a single cache
> entry that'd "upgrade" itself to be an index (have the ords).  This
> single entry could then serve ords, ords+terms, or just terms.

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message