Last modified: 2014-05-08 20:56:37 UTC
issuing the following query (and following the sequence of cocontinue parameters): http://en.wikipedia.org/w/api.php?action=query&prop=coordinates&format=json&colimit=1&coprop=globe&coprimary=primary&titles=Montreal%7CParis%7CToronto%7CSherbrooke%7CQuebec returns only 3 distinct coordinates whereas issuing the following query: http://en.wikipedia.org/w/api.php?action=query&prop=coordinates&format=json&colimit=5&coprop=globe&coprimary=primary&titles=Montreal%7CParis%7CToronto%7CSherbrooke%7CQuebec returns 5 distinct coordinates. The difference between the 2 queries is that the first uses a colimit=1 and the second uses a colimit=5. The returned result set Must be independent of whether or not the cocontinue mechanism was used to get the result. The queried API endpoint is http://en.wikipedia.org/w/api.php (dont know which version that is?). Any feedback appreciated!
The prop=coordinates module is provided by the GeoData extension, reassigning there and confirming the bug. At a glance, it looks like the bug is that the SQL query fragment for continuation is "gt_page_id > {$parts[0]} OR (gt_page_id = {$parts[0]} AND gt_id > {$parts[1]})" where it should have "gt_id >= {$parts[1]}" at the end instead.
Change 132208 had a related patch set uploaded by MaxSem: Fix prop=coordinates continuation https://gerrit.wikimedia.org/r/132208
Change 132208 merged by jenkins-bot: Fix prop=coordinates continuation https://gerrit.wikimedia.org/r/132208
The fix should be deployed to WMF wikis with 1.24wmf5, see https://www.mediawiki.org/wiki/MediaWiki_1.24/Roadmap for the schedule.
That was fast. Good work !
