Description

in origin_get_range and origin_search.

URL hashes would be the obvious solution as pagination index, but that wouldn't work efficiently with Cassandra (although it's possible).

I propose we move to opaque tokens.

(This could also be extended to all other endpoints in the future, as each currently has its own scheme and argument names for pagination.)

We also need to find a name for this token, as the same mechanism will be used in multiple components and endpoints, eg:

Revisions and Commits

rDSTO Storage manager
	Closed	D2343 Add Storage.content_get_partition endpoint, to replace content_get_range.
	Closed	D2324 Add endpoint 'origin_list', that will replace 'origin_get_range'.

Status	Assigned	Task
Migrated	gitlab-migration	T2213 Storage
Migrated	gitlab-migration	T2214 Scale-out graph and database storage in production
Migrated	gitlab-migration	T1892 Cassandra as a storage backend
Migrated	gitlab-migration	T2194 Archive Integration (Web API)
Migrated	gitlab-migration	T2195 Web API 2
Migrated	gitlab-migration	T1805 Public API v2
Migrated	gitlab-migration	T1912 Support origin pagination without origin ids