Page MenuHomePhabricator

Paginate statements in GET /entities/items/{item_id}/statements
Open, Stalled, Needs TriagePublic

Description

As an app developer I want to enumerate through item's statement so that I can use all their data in my application

See offset, page, per_page parameters in the API Proposal

  • default per_page value, if not given: 50
  • possible maximum limit for per_page TBD

Meta info on pagination (which page are we on? how many total entries and/or pages do we have?) included in the response headers: TBD

Event Timeline

WMDE-leszek changed the task status from Open to Stalled.Apr 27 2022, 6:45 PM

Marking this as stalled. The purpose of providing only limited amount of data should, at least partly, be performance. Given how Wikiabse stores data, all statements are loaded from the database, regardless if the API user would ask for 10 or all 15000 of those. While pagination seems like a meaningful functionality, and Wikibase API providing always all the data seems not ideal, meaningfully providing subset of data would require some fundamental changes in how the data is stored.
This task can be revisited while performance goals of Wikibase and Wikidata have been revisited in this context.

Would it make sense to close this and open as the need arises?