[
https://issues.apache.org/jira/browse/LUCENE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Klaas updated LUCENE-850:
------------------------------
Attachment: CustomBoostQuery.java
Here's an approach I think will work.
Rename CustomScoreQuery to CustomBoostQuery, and remove the
ValueSource-specific logic. Really there is no reason to limit the logic to
ValueSource queries: the only important criterion is that we don't expect the
docs matches against the boosting query only to be returned (the doc set is
unchanged relative to the original query).
I'm not sure what will happen if the boost query doesn't match the document
being boosted, however. Perhaps there should be a default value?
Does this still belong in the function package?
> Easily create queries that transform subquery scores arbitrarily
> ----------------------------------------------------------------
>
> Key: LUCENE-850
> URL: https://issues.apache.org/jira/browse/LUCENE-850
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Search
> Reporter: Mike Klaas
> Attachments: CustomBoostQuery.java, prodscorer.patch.diff
>
>
> Refactor DisMaxQuery into SubQuery(Query|Scorer) that admits easy
> subclassing. An example is given for multiplicatively combining scores.
> Note: patch is not clean; for demonstration purposes only.
--
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]
