lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-6198) two phase intersection
Date Thu, 12 Feb 2015 17:06:13 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318557#comment-14318557
] 

Robert Muir commented on LUCENE-6198:
-------------------------------------

Yes, I think thats good to show it has nice speedups for positions queries even in the smallish
case (1KB docs). I think if you ran this on the full documents, e.g. wikibig, it would be
more dramatic.

> two phase intersection
> ----------------------
>
>                 Key: LUCENE-6198
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6198
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Robert Muir
>         Attachments: LUCENE-6198.patch, LUCENE-6198.patch, LUCENE-6198.patch, LUCENE-6198.patch,
phrase_intersections.tasks
>
>
> 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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message