[zope2-tracker] [Bug 815469] [NEW] ZCatalog 2.13.12 doesn't preserve relevance in search results
Ross Patterson
me at rpatterson.net
Sun Jul 24 12:21:50 EDT 2011
Public bug reported:
The change log for ZCatalog 2.13.12 says:
"Replaced `weightedIntersection` and `weightedUnion` calls with their
non-weighted version, as we didn't pass in weights."
But the BTrees.Interfaces documents:
"def weightedIntersection(c1, c2, weight1=1, weight2=1)"
Meaning that by default, both results sets are given equal weight. IOW,
the wieghts provided by _apply_index still have an effect when weight1
and weight2 are not provided. I have tests asserting relevance in
search results order that pass under previous versions but fail under
this version. Please restore the use of weightedIntersection.
** Affects: zope2
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.
https://bugs.launchpad.net/bugs/815469
Title:
ZCatalog 2.13.12 doesn't preserve relevance in search results
To manage notifications about this bug go to:
https://bugs.launchpad.net/zope2/+bug/815469/+subscriptions
More information about the zope2-tracker
mailing list