[
https://issues.apache.org/jira/browse/LUCENE-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2093.
----------------------------------------
Resolution: Fixed
Fix Version/s: (was: 4.1)
4.0
5.0
We've improved queries so they now save their own term state during rewrite and
re-use it during matching.
> Use query-private scope instead of shared Term->TermInfo cache
> --------------------------------------------------------------
>
> Key: LUCENE-2093
> URL: https://issues.apache.org/jira/browse/LUCENE-2093
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Reporter: Michael McCandless
> Priority: Minor
> Fix For: 5.0, 4.0
>
>
> Spinoff of LUCENE-2075.
> We currently use a shared terms cache so multiple resolves of the same term
> within execution of a single query save CPU. But this ties up a good amount
> of long term RAM...
> So, it might be better to instead create a "query private scope", where
> places in Lucene like the terms dict could store & retrieve results. The
> scope would be private to each running query, and would be GCable as soon as
> the query completes. Then we've have perfect within query hit rate...
--
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: [email protected]
For additional commands, e-mail: [email protected]
