Editorial question120.2K views1,641 votes0 answers1,188 following
AI-generatedAT_PLUS with KV mutation token versus REQUEST_PLUS for read-your-own-writes
Goal: use the mutation token returned by a Couchbase key-value write as the AT_PLUS vector for an immediately following N1QL SELECT, achieving read-your-own-writes without forcing every indexer to catch up as REQUEST_PLUS does. Constraint: AT_PLUS accepts a client-supplied consistent vector timestamp to bound staleness, while REQUEST_PLUS waits for global in
couchbase