[ 
https://issues.apache.org/jira/browse/LUCENE-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553232
 ] 

Hoss Man commented on LUCENE-1093:
----------------------------------

NOTE: this should be an option, not a change to the default behavior (right now 
a SpanFirstQuery always returns Spans the same size as it's subquery ... 
changing this could radically affect the scores users get from existing queries.

API that seems like it would make the most sense is a new boolean getter/setter 
that defaults to false ... no idea what agood descriptive name for it would be.


(I too thought we added this a long time ago, i remember asking about it when i 
was writing  unit tests for SpanQuery.explain)

> SpanFirstQuery modification to aid term boosting based on position.
> -------------------------------------------------------------------
>
>                 Key: LUCENE-1093
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1093
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Query/Scoring
>            Reporter: Peter Keegan
>
> This is a request for a modification to SpanFirstQuery that would allow term 
> boosting based on a term's distance from the beginning of the document.
> This modification to SpanFirstQuery would be that the Spans returned by 
> SpanFirstQuery.getSpans() must always return 0 from its start() method. Then 
> the slop passed to sloppyFreq(slop) would be the distance from the beginning 
> of the indexed field to the end of the Spans of the SpanQuery passed to 
> SpanFirstQuery.
> Here is the discussion behind this issue:
> http://www.nabble.com/Can-I-do-boosting-based-on-term-postions--to11939423.html#a11939423

-- 
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]

Reply via email to