lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Khludnev (JIRA)" <>
Subject [jira] [Commented] (LUCENE-5460) Allow driving a query by sparse filters
Date Fri, 28 Mar 2014 20:03:19 GMT


Mikhail Khludnev commented on LUCENE-5460:

Would you mind if I ask you to review the proposal attached? I suppose it can be beneficial
as a new Lucene ability. Please look at it!

> Allow driving a query by sparse filters
> ---------------------------------------
>                 Key: LUCENE-5460
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/search
>            Reporter: Shai Erera
>         Attachments:
> Today if a filter is very sparse we execute the query in sort of a leap-frog manner between
the query and filter. If the query is very expensive to compute, and/or matching few docs
only too, calling scorer.advance(doc) just to discover the doc it landed on isn't accepted
by the filter, is a waste of time. Since Filter is always the "final ruler", I wonder if we
had something like {{boolean DISI.advanceExact(doc)}} we could use it instead, in some cases.
> There are many combinations in which I think we'd want to use/not-use this API, and they
depend on: Filter's complexity, Filter.cost(), Scorer.cost(), query complexity (span-near,
many clauses) etc.
> I open an issue so we can discuss. DISI.advanceExact(doc) is just a preliminary proposal,
to get an API we could experiment with. The default implementation should be fairly easy and
straightforward, and we could override where we can offer a more optimized imp.

This message was sent by Atlassian JIRA

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

View raw message