Opened 16 years ago
Closed 15 years ago
#386 closed defect (fixed)
Use of match spies results in poor lower bound on number of results
Reported by: | Richard Boulton | Owned by: | Olly Betts |
---|---|---|---|
Priority: | normal | Milestone: | 1.1.3 |
Component: | Library API | Version: | SVN trunk |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Operating System: | All |
Description
When a match spy is used, even if the match spy never returns false (to exclude a matching document), the lower bound on the number of results is reduced to the number of results actually seen. This is necessary because Xapian has no way to know whether the match spy might exclude documents which haven't been seen.
It would be nice for there to be a way to tell Xapian that a match spy will never exclude any documents from the search results; perhaps this could be a flag which can be read from the matchspy somehow, or perhaps it could be an option passed to enquire when the matchspy is set.
Change History (1)
comment:1 by , 15 years ago
Milestone: | → 1.1.3 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
This has already been resolved in trunk (and will be in 1.1.3) - there's now a dedicated MatchSpy class which can only observe and not reject documents.