Fusion Tables shutdown leaves OFFSET pagination of large filtered queries unspecified

Google Fusion Tables exposed a SQL-like query language in which a SELECT could include LIMIT and OFFSET, while result sizes were also bounded server-side by per-query caps that varied by user role. No cursor or keyset mechanism was documented, so OFFSET paging was the documented approach for walking a large filtered result set.

The archived query-language documentation does not state whether OFFSET paging remained stable when rows were inserted, updated, or deleted between page fetches, or how the server-side cap composed with OFFSET: whether it bounded only the returned page or the whole addressable range. Because the API was deprecated in 2013 and the service shut down in December 2019, these semantics can only be assessed against archived material rather than a live endpoint.

For a migration design that must describe how large filtered result sets were paged, the unresolved points are: did the documented LIMIT/OFFSET semantics imply a deterministic page sequence across concurrent edits, and did the per-query result cap make deep OFFSET pages unreachable once OFFSET plus LIMIT exceeded the cap?