You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2010/12/28 06:08:45 UTC

[jira] Resolved: (LUCENE-2835) FieldCache rewrite method for MultiTermQueries

     [ https://issues.apache.org/jira/browse/LUCENE-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir resolved LUCENE-2835.
---------------------------------

    Resolution: Duplicate

sorry, JIRA puked and i ended up with a duplicate issue.

> FieldCache rewrite method for MultiTermQueries
> ----------------------------------------------
>
>                 Key: LUCENE-2835
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2835
>             Project: Lucene - Java
>          Issue Type: New Feature
>            Reporter: Robert Muir
>             Fix For: 4.0
>
>
> For some MultiTermQueries, like RangeQuery we have a FieldCacheRangeFilter etc (in this case its particularly optimized).
> But in the general case, since LUCENE-2784 we can now have a rewrite method to rewrite any MultiTermQuery 
> using the FieldCache, because MultiTermQuery's getEnum no longer takes IndexReader but Terms, and all the 
> FilteredTermsEnums are now just real TermsEnum decorators.
> In cases like low frequency queries this is actually slower (I think this has been shown for numeric ranges before too),
> but for the really high-frequency ones like especially ugly wildcards, regexes, fuzzies this can be many times faster 
> using the FieldCache instead, since all the terms are in RAM and automaton can blast through them quicker.

-- 
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