Changes in xapian/xapian-core/ xapian/xapian-core/matcher/

Sam Liddicott <sam <at> ixion.tartarus.org>
2003-03-06 11:37:27 GMT

CVS Root: /usr/data/cvs
Module: xapian
Changes by: sam
Date: Thu Mar 06 2003 11:37:27 GMT
Log message:
Added code to track the weight of the highest collapsed document for each
collapse key value, so that just before returning the mset we can check for
each collapse key if at least one (the highest) document that has been collapsedaway would have been
relevent enough to be over the threshold.
If this is not the case, we adjust collapse_count to zero.
It msut be understood (and I will write this up) that a collapse-count of zero does not mean there are no
documents relevent enough that would collapse, it only means none were discovered during the optimised search.
Now, however, a collapse count of >=1 does mean there exists at least one other
document that collapsed that would have been shown in one of the pages of results
Modified files:
xapian-core : ChangeLog
xapian-core/matcher: multimatch.cc
Links:
http://xapian.org/C?xapian/xapian-core/ChangeLog?1.1795?1.1796http://xapian.org/C?xapian/xapian-core/matcher/multimatch.cc?1.144?1.145
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com