[
https://issues.apache.org/jira/browse/LUCENE-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975477#action_12975477
]
Uwe Schindler commented on LUCENE-2836:
---------------------------------------
Hah, cool!
The question is, does it really works correct with multivalued fields? I have
to recapitulate the TermsIndex, but the method fcsi.getOrd(doc) returns only
the term ord of the first term found in index for that document? For numeric
queries with single-value fields thats fine, but for wildcards on analyzed
fields? Maybe I miss something, but I am not sure if it works correct...
Robert: Help me please :-) *g*
> FieldCache rewrite method for MultiTermQueries
> ----------------------------------------------
>
> Key: LUCENE-2836
> URL: https://issues.apache.org/jira/browse/LUCENE-2836
> Project: Lucene - Java
> Issue Type: New Feature
> Reporter: Robert Muir
> Fix For: 4.0
>
> Attachments: LUCENE-2836.patch
>
>
> 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 cases like especially ugly wildcards,
> regexes, fuzzies, etc, this can be several 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: [email protected]
For additional commands, e-mail: [email protected]
