[
https://issues.apache.org/jira/browse/LUCENE-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-2190.
-----------------------------------
Resolution: Fixed
Assignee: Uwe Schindler (was: Michael McCandless)
Lucene Fields: [New, Patch Available] (was: [New])
Committed 3.0 branch revision: 912383, 912389
Committed trunk revision: 912386
Committed 2.9 branch revision: 912390
Thanks Mike for the help!
> CustomScoreQuery (function query) is broken (due to per-segment searching)
> --------------------------------------------------------------------------
>
> Key: LUCENE-2190
> URL: https://issues.apache.org/jira/browse/LUCENE-2190
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.9, 2.9.1, 3.0, 3.0.1, 3.1
> Reporter: Michael McCandless
> Assignee: Uwe Schindler
> Fix For: 2.9.2, 3.0.1, 3.1
>
> Attachments: LUCENE-2190-2-branch29.patch,
> LUCENE-2190-2-branch30.patch, LUCENE-2190-2-branch30.patch,
> LUCENE-2190-2-trunk.patch, LUCENE-2190-2-trunk.patch, LUCENE-2190-2.patch,
> LUCENE-2190-2.patch, LUCENE-2190.patch
>
>
> Spinoff from here:
> http://lucene.markmail.org/message/psw2m3adzibaixbq
> With the cutover to per-segment searching, CustomScoreQuery is not really
> usable anymore, because the per-doc custom scoring method (customScore)
> receives a per-segment docID, yet there is no way to figure out which segment
> you are currently searching.
> I think to fix this we must also notify the subclass whenever a new segment
> is switched to. I think if we copy Collector.setNextReader, that would be
> sufficient. It would by default do nothing in CustomScoreQuery, but a
> subclass could override.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
