[LUCENE-1019] CustomScoreQuery should support multiple ValueSourceQueries

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.2
• Fix Version/s: 2.3
• Component/s: core/search
• Lucene Fields: Patch Available
• Assignee: Doron Cohen
• Reporter: Kyle Maxwell
• Created: 05/Oct/07 01:06
• Updated: 28/Aug/22 11:41
• Resolved: 13/Dec/07 06:32

Description

CustomScoreQuery's constructor currently accepts a subQuery, and a ValueSourceQuery. I would like it to accept multiple ValueSourceQueries. The workaround of nested CustomScoreQueries works for simple cases, but it quickly becomes either cumbersome to manage, or impossible to implement the desired function.

This patch implements CustomMultiScoreQuery with my desired functionality, and refactors CustomScoreQuery to implement the special case of a CustomMultiScoreQuery with 0 or 1 ValueSourceQueries. This keeps the CustomScoreQuery API intact.

This patch includes basic tests, more or less taken from the original implementation, and customized a bit to cover the new cases.

Issue Links

• relates to: LUCENE-1085 search.function should support all capabilities of Solr's search.function