[ https://issues.apache.org/jira/browse/LUCENE-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378778#comment-14378778 ]
Paul Elschot commented on LUCENE-6198: -------------------------------------- bq. I'm curious if you have ideas to take advantage of approximations in another context than scorers? Approximations are being added to Spans in LUCENE-6308. > two phase intersection > ---------------------- > > Key: LUCENE-6198 > URL: https://issues.apache.org/jira/browse/LUCENE-6198 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Robert Muir > Assignee: David Smiley > Fix For: Trunk, 5.1 > > Attachments: LUCENE-6198.patch, 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org