[
https://issues.apache.org/jira/browse/LUCENE-5429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-5429:
---------------------------------------
Attachment: LUCENE-5429.patch
Patch, making a Similarity that switches between sub-Sims, and a custom
collector that uses that switching and calls .score() and then collects into
multiple sub-Collectors.
While this works for TermQuery, and all-MUST BooleanQuery, the test fails on
all-SHOULD BooleanQuery because DisjunctionSum/MaxScorer pre-compute the score
during matching. I know they do this for performance reasons (single pass
recursion through the PQ to find the sub-scorers that matched)... so I think
the only way this feature can work in general is with a custom BQ that doesn't
do this opto.
> Run one search across multiple scorers/collectors
> -------------------------------------------------
>
> Key: LUCENE-5429
> URL: https://issues.apache.org/jira/browse/LUCENE-5429
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Attachments: LUCENE-5429.patch
>
>
> I'm looking into the possibility of running the same search across many
> scorers, so that decoding postings lists / doing union and intersect are done
> once, but scoring via Similarity can be done multiple times for each it (and
> the results collected into separate collectors).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
