Redis RediSearch LIMIT offset semantics for deep pagination

Goal

We want to paginate a large result set from a RediSearch query in a user‑facing application.

Constraints & Uncertainty

RediSearch applies the LIMIT offset count after sorting, so deep offsets (e.g., 10 000) can become expensive and may skip items if the index changes between requests. Concurrent updates or deletes can shift document rankings, causing the same offset to return different items in successive queries. No cursor‑based API exists; developers must rely on LIMIT or custom application logic.

Open Questions

• What strategies can guarantee deterministic pagination when using LIMIT with large offsets in a mutable index?
• Does RediSearch provide any internal mechanism or recommended pattern to implement cursor‑based pagination that mitigates the offset performance and consistency issues?