Issue 2550635
Created on 2010-02-05 15:22 by wolever, last changed 2013-10-21 11:21 by ThomasAH.
|
| msg4020 |
Author: [hidden] (wolever) |
Date: 2010-02-05 15:22 |
|
Reading through the Xapian indexer's code, I noticed this in 'find':
query = xapian.Query(xapian.Query.OP_AND, terms)
enquire.set_query(query)
matches = enquire.get_mset(0, 10) <<<<< THIS LINE
return [tuple(m[xapian.MSET_DOCUMENT].get_data().split(':'))
for m in matches]
It looks like only the first 10 results will be returned… Is that expected?
|
| msg4503 |
Author: [hidden] (ced) |
Date: 2012-02-28 17:04 |
|
I think it could be increased at least to 50 as it is the default paging.
|
| msg4504 |
Author: [hidden] (ced) |
Date: 2012-02-29 14:18 |
|
I just increase it on our instance to 5000 because users complains about
missing result in the text search.
Indeed as others indexers don't have such limit, I think xapian should
also not have a limit. I read the xapian doc but I did not find how to
fetch all the result without limit.
|
| msg4939 |
Author: [hidden] (ThomasAH) |
Date: 2013-10-21 11:10 |
|
https://sourceforge.net/p/roundup/code/ci/3ff1a288fb9c
changeset: 4841:3ff1a288fb9c
tag: tip
user: Thomas Arendsen Hein <thomas@intevation.de>
date: Mon Oct 21 12:56:28 2013 +0200
summary: issue2550583, issue2550635 Do not limit results with Xapian
indexer
|
|
| Date |
User |
Action |
Args |
| 2013-10-21 11:21:03 | ThomasAH | set | status: new -> fixed |
| 2013-10-21 11:10:32 | ThomasAH | set | superseder: xapian search yields too few results
messages:
+ msg4939
priority: high
assignee: ThomasAH
nosy:
+ ThomasAH
resolution: fixed |
| 2012-02-29 14:18:13 | ced | set | messages:
+ msg4504 |
| 2012-02-28 17:04:43 | ced | set | messages:
+ msg4503 |
| 2012-02-28 17:01:49 | ced | set | nosy:
+ ced |
| 2010-10-25 00:43:13 | bruce | set | nosy:
+ bruce |
| 2010-02-05 15:22:41 | wolever | create | |
|