Brendan Clement b4bafa38f6 docs: correct grant pagination and the two read-freshness watermarks ...

A grant listing was said to hold at most 100 entries a page. The server
counts 100 stored (object, subject) tuples a page and then expands each
into its privileges, so a page can return more; the page now says so
and to keep requesting with the token.

The consistency page said a write's version is never used to choose
what a read sees. The client sends two version headers: the write
result in x-lancedb-min-version, which deployments ignore, and the
highest version any response reported in x-lancedb-min-read-version,
which they check. A successful write's response advances the second.
The page now separates them and keeps the advice to read with a zero
interval or after checkout_latest when a read must reflect a write.

2026-10-09 13:33:32 -07:00

..

authorization.mdx

docs: correct grant pagination and the two read-freshness watermarks

2026-10-09 13:33:32 -07:00