Yonik Seeley wrote:
As far as API goes, I guess there should be a constructor ConstantScoreQuery(Filter filter, String field) If field is non-null, then the field norm can be multiplied into the score.
You could implement this with a scorer subclass that multiplys by the norm, removing a conditional from the inner loop.
Now how would the user go about choosing a truely constant scoring range query vs a constant scoring range query with the norms folded in? An additional flag called includeFieldBoost on ConstantScoreRangeQuery?
Sounds good to me. Doug --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
