lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] Updated: (LUCENE-1790) Add Boosting Function Term Query and Some Payload Query refactorings
Date Sat, 15 Aug 2009 19:05:14 GMT


Mark Miller updated LUCENE-1790:

    Attachment: LUCENE-1790.patch

remove some unused imports
added missing license header

Added hashCode to BoostingFunctionTermQuery

Added hashCode/equals to PayloadFunction classes

added hashcode/equals to query - really it should be handling the equals/hashcode for boost,
not subclasses (which will be likely to forget it - you should check super classes for these
things anyway as well).

BoostingFunctionTermQuery is a subclass of SpanTermQuery, but both of them use a weak equals
method (using instanceof)
so while BoostingFunctionTermQuery.equals(SpanTermQuery) should equal SpanTermQuery.equals(BoostFunctionTermQuery),
it doesn't.

Added new hashCode/equals for both classes that work properly.

Added a couple tests for these fixes

> Add Boosting Function Term Query and Some Payload Query refactorings
> --------------------------------------------------------------------
>                 Key: LUCENE-1790
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>            Reporter: Grant Ingersoll
>            Assignee: Grant Ingersoll
>            Priority: Minor
>             Fix For: 2.9
>         Attachments: LUCENE-1790-position.patch, LUCENE-1790.patch, LUCENE-1790.patch,
LUCENE-1790.patch, LUCENE-1790.patch
> Similar to the BoostingTermQuery, the BoostingFunctionTermQuery is a SpanTermQuery, but
the difference is the payload score for a doc is not the average of all the payloads, but
applies a function to them instead.  BoostingTermQuery becomes a BoostingFunctionTermQuery
with an AveragePayloadFunction applied to it.
> Also add marker interface to indicate PayloadQuery types.  Refactor Similarity.scorePayload
to also take in the doc id.

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:
For additional commands, e-mail:

View raw message