Get Update Status
Get how far record changes have been applied: the last accepted and the last applied seq.
Authentication
A write key, issued by Captain. Server side only. Sent as Authorization: Bearer <key>.
Path parameters
Response headers
the last update seq search had applied when this request started; the answer reflects at least that much (GET .../updates applied_seq). Not on 401 or 403, nor for an index this server does not have
the index's incarnation, an opaque string: it changes only when the index is deleted and created again (whose seqs start again at 1), or restored from a backup (whose seqs continue from the backup's). Sent with X-Captain-Applied-Seq
Response
the index's incarnation, the same value as the X-Captain-Index-Incarnation header: it changes only when the index is deleted and created again, or restored from a backup. Seqs from different incarnations are not comparable
the last seq whose added and replaced records match keyword searches (names, brands, SKUs). It is never below applied_seq.
the last seq that search has fully applied: added and replaced records are fully searchable, with semantic matching and their final ranking
on servers that build by themselves (App Search): where the automatic build stands. Small adds are searchable before it runs (keyword_seq, then applied_seq); larger ones when it finishes
present while a backup holds: updates are accepted and applied when it ends
with paused: unix seconds when the hold ends at the latest
Beta. When added records waiting for a build, or being built, will be searchable, from the work ahead of them and this tenant's recent build speeds; null when nothing waits (service/eta.py)