Closed Bug 876384 Opened 13 years ago Closed 13 years ago

Some of the calls to the search API doesn't return all the objects they should

Categories

(Marketplace Graveyard :: Search, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED
2013-06-27

People

(Reporter: nati, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31 Steps to reproduce: e.g. requested https://marketplace.firefox.com/api/v1/apps/search/?limit=20&offset=140 (it seems like there is a problem with specific applications, for example: https://marketplace.firefox.com/api/v1/apps/search/?limit=1&offset=152) Actual results: got 19 objects Expected results: 20 objects should be returned
Something like this can happen when our search index becomes out of sync with our database.
Component: API → Search
It seems like this is always the case. Although the above links might work now, iterating over all the apps (empty query), return less apps than advertised in meta.total_count
(In reply to nati from comment #2) > It seems like this is always the case. > Although the above links might work now, iterating over all the apps (empty > query), return less apps than advertised in meta.total_count Right. Once it's out of sync we'll either need to re-index or find the app that is out of sync manually and fix. Note: We're currently testing a new search index that should fix this.
Is there another method to iterate over all apps other than an empty search query?
(In reply to nati from comment #4) > Is there another method to iterate over all apps other than an empty search > query? No, but the bulk exports are going live today at 2pm so you could use that for your indexing. (This bug is still valid so leaving it open)
Priority: -- → P3
We've since replaced our search indexing and this appears to be fixed now. Re-open if you find again.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-06-27
You need to log in before you can comment on or make changes to this bug.