DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33019>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33019 ------- Additional Comments From [EMAIL PROTECTED] 2005-01-19 21:12 ------- For this to work correctly the list of valid buckets should always be sorted, ie. it is necessary to uncomment the sorting call in added in next(). Otherwise next() might return a higher document number than skipTo() would skip to, ie. a lower document number would not be scored at all. In that case the implementation of skipTo can also be simplified somewhat because it would only have to delete from the beginning of the valid bucket list. I think a version of BooleanScorer modified with this patch could be used as a BooleanSubScorer. As a top level scorer, BooleanScorer is difficult to beat in performance for non required clauses, and on the top level it is not a problem that documents are not processed strictly in order, normally they will be used in a Hits that presents them in another other anyway. For a non top level scorer, or when the document order should be followed strictly, the patched version could be used as BooleanSubScorer, or the DisjunctionScorer posted earlier could be used. Below top level, DisjunctionScorer could be faster because it never works ahead into a bucket list. A strict document order would also be an advantage when creating an IterFilter from a BooleanQuery. Regards, Paul Elschot -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
