lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrien Grand (JIRA)" <>
Subject [jira] [Updated] (LUCENE-6198) two phase intersection
Date Wed, 11 Feb 2015 14:47:12 GMT


Adrien Grand updated LUCENE-6198:
    Attachment: LUCENE-6198.patch

> two phase intersection
> ----------------------
>                 Key: LUCENE-6198
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Robert Muir
>         Attachments: LUCENE-6198.patch, LUCENE-6198.patch
> Currently some scorers have to do a lot of per-document work to determine if a document
is a match. The simplest example is a phrase scorer, but there are others (spans, sloppy phrase,
geospatial, etc).
> Imagine a conjunction with two MUST clauses, one that is a term that matches all odd
documents, another that is a phrase matching all even documents. Today this conjunction will
be very expensive, because the zig-zag intersection is reading a ton of useless positions.
> The same problem happens with filteredQuery and anything else that acts like a conjunction.

This message was sent by Atlassian JIRA

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

View raw message