Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Message-ID: <14012421.13861274278854596.JavaMail.jira@thor>
Date: Wed, 19 May 2010 10:20:54 -0400 (EDT)
From: "Peter Keegan (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Subject: [jira] Updated: (LUCENE-2272) PayloadNearQuery has hardwired
 explanation for 'AveragePayloadFunction'
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/LUCENE-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Keegan updated LUCENE-2272:
---------------------------------

    Attachment: PNQ-patch1.txt

Revisiting this because the PayloadFunction 'explain' methods return the wrong value and aren't thread safe, as Grant points out. A new patch is attached which eliminates the member variables.

> PayloadNearQuery has hardwired explanation for 'AveragePayloadFunction'
> -----------------------------------------------------------------------
>
>                 Key: LUCENE-2272
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2272
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Search
>            Reporter: Peter Keegan
>            Assignee: Grant Ingersoll
>         Attachments: payloadfunctin-patch.txt, PNQ-patch.txt, PNQ-patch1.txt
>
>
> The 'explain' method in PayloadNearSpanScorer assumes the AveragePayloadFunction was used. This patch adds the 'explain' method to the 'PayloadFunction' interface, where the Scorer can call it. Added unit tests for 'explain' and for {Min,Max}PayloadFunction.

-- 
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org