[
https://issues.apache.org/jira/browse/LUCENE-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Keegan updated LUCENE-1341:
---------------------------------
Attachment: lucene-1341-new-1.patch
As I was debugging a unit test for BoostingNearQuery, I discovered that not all
the payloads were getting read. The 'needToLoadPayload' flag on the termpos was
getting reset on the last term in the span by NearSpansOrdered. Then I noticed
that the term positions aren't even needed in BNQ because they were already
collected by the Spans in 'matchPayload'. So, here is a newer, simpler
implementation of BNQ along with some unit tests.
Peter
> BoostingNearQuery class (prototype)
> -----------------------------------
>
> Key: LUCENE-1341
> URL: https://issues.apache.org/jira/browse/LUCENE-1341
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Query/Scoring
> Affects Versions: 2.3.1
> Reporter: Peter Keegan
> Assignee: Grant Ingersoll
> Priority: Minor
> Fix For: 3.0
>
> Attachments: bnq.patch, bnq.patch, BoostingNearQuery.java,
> BoostingNearQuery.java, lucene-1341-new-1.patch, LUCENE-1341-new.patch,
> LUCENE-1341.patch
>
>
> This patch implements term boosting for SpanNearQuery. Refer to:
> http://www.gossamer-threads.com/lists/lucene/java-user/62779
> This patch works but probably needs more work. I don't like the use of
> 'instanceof', but I didn't want to touch Spans or TermSpans. Also, the
> payload code is mostly a copy of what's in BoostingTermQuery and could be
> common-sourced somewhere. Feel free to throw darts at 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: [email protected]
For additional commands, e-mail: [email protected]
