Last modified: 2010-01-16 19:06:21 UTC
Not quite sure if this is really an API bug, or a search bug.. Or what... Or whether its a WMF/Lucene implimented limitation. If you use srlimit=max, or anything above (No more than 50 (500 for bots) allowed.), no offset is given for continuing. Using anything below, does If this is enforced behaviour (due to WMF, Lucene, or similar), the API documentation should be updated to this effect (ie the help the API provides). <limits search="500" /> also sporadicly appears. What is that?
(In reply to comment #0) > Not quite sure if this is really an API bug, or a search bug.. Or what... Or > whether its a WMF/Lucene implimented limitation. > > If you use srlimit=max, or anything above (No more than 50 (500 for bots) > allowed.), no offset is given for continuing. Using anything below, does > Are you sure there *is* anything to continue? Try srlimit=30 (300 if you're a bot) and continuing once to find out. > If this is enforced behaviour (due to WMF, Lucene, or similar), the API > documentation should be updated to this effect (ie the help the API provides). > Not sure what causes this yet, will investigate. > <limits search="500" /> also sporadicly appears. What is that? > That shows up when using srlimit=max . It's the API's way of telling you what it translated "max" to.
I've put the maximum on the backend to 50 in order to prevent overloads. Will be enforced at least until new servers get it.
Roan, searching for "test" will most certainly find more than 50.. http://en.wikipedia.org/w/api.php?action=query&list=search&srwhat=text&srsearch=all:'test'&srlimit=max <searchinfo totalhits="2443730" /> Robert, thanks for this information. Presumably why its showing a larger result set, than the full 500 it's supposed to be returning (what the api is reporting). IMHO then, its not really a bug, or at least, less of (changing to enhancement), we just could ideally do with a comment (really only on the wmf version.. Unless with the lucene search extension we can grab check a variable to find the limits that are being imposed)
Haven't the search limits been increased again...?
(In reply to comment #4) > Haven't the search limits been increased again...? > Yes, the backend limit has been increased again. Per Robert the API limit is still at 50, which means that at least normal operation with srlimit < 50 should work again. Setting srlimit equal to 500 is probably still broken (please test this); if it is, I'll ask Robert to raise the limit to 501 as a workaround.
Ok, as a sysop (against en.wp), max gives 500. Setting the limit to 500 gives 499. So presumably, if we can get this change to 501 on the search end, this can be marked as fixed/resolved.
The max on the backend is 501 for more than a week now.
Seems I must've miscopied. Just checked and it is. Marking as fixed. Thanks!
