[
https://issues.apache.org/jira/browse/LUCENE-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292827#comment-14292827
]
Robert Muir commented on LUCENE-6198:
-------------------------------------
I think i already said, i don't like many things about it when uploading the
patch.
Its obviously not a great API, but has other benefits like keeping performance
fast, backwards compatibility (without introducing scary bugs into peoples
code), can work for both Query+Filter, etc.
Its also unfortunately far easier to suggest more complicated API as a comment,
than to suggest actual patches for this issue. Its a shitload of work if you
want to implement things efficiently for these scorers and not screw up
performance.
I don't want to argue about it, i know the patch i proposed sucks, its like
going fishing, this time just didnt catch anything. move on to another lake or
another sport instead.
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
