lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Willnauer (JIRA)" <>
Subject [jira] [Created] (LUCENE-4410) Make FilteredQuery more flexible with regards to how filters are applied
Date Thu, 20 Sep 2012 09:58:07 GMT
Simon Willnauer created LUCENE-4410:

             Summary: Make FilteredQuery more flexible with regards to how filters are applied
                 Key: LUCENE-4410
             Project: Lucene - Core
          Issue Type: Improvement
          Components: core/search
    Affects Versions: 4.0-BETA
            Reporter: Simon Willnauer
            Priority: Blocker
             Fix For: 5.0, 4.0

Currently FilteredQuery uses either the "old" lucene 3 leap frog approach or pushes the filter
down together with accepted docs. Yet there might be more strategies required to fit common
usecases like geo-filtering where a rather costly function is applied to each document. Using
leap frog this might result in a very slow query if the filter is advanced since it might
have linear running time to find the next valid document. We should be more flexible with
regards to those usecases and make it possible to either tell FQ what to do or plug in a strategy
that applied a filter in a different way.

The current FQ impl also uses an heuristic to decide if RA or LeapFrog should be used. This
is really an implementation detail of the strategy and not of FQ and should be moved out.

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