lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Ingersoll (JIRA)" <>
Subject [jira] Updated: (LUCENE-1790) Boosting Function Term Query
Date Fri, 07 Aug 2009 20:15:15 GMT


Grant Ingersoll updated LUCENE-1790:

    Attachment: LUCENE-1790.patch

Next take on this:

1. Added includeSpanScore flag, which allows you to ignore the score from the TermQuery part
of the score and only count the payload.

2. Deprecated Similarity.scorePayload(String fieldName, ...) to a similar method that also
takes in the Doc id.  Now, in theory, you could have different scoring for payloads based
on different documents, fields, etc.  The old method just calls the new one and passes in
a NO_DOC_ID_PROVIDED value (-1).

3. Added a Marker Interface named PayloadQuery and marked the various PayloadQueries.  This
could be useful for Queries that work with other PayloadQueries (more exclusive than the fact
that they are SpanQueries.

I really do intend to commit this :-)

> Boosting Function Term Query
> ----------------------------
>                 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.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.

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