Skip to content

docs: clarify read consistency behavior for db:// remote tables#276

Open
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/c2aaa682
Open

docs: clarify read consistency behavior for db:// remote tables#276
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/c2aaa682

Conversation

@mintlify

@mintlify mintlify Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Summary

Update the consistency guide so its description of read-your-write behavior matches what the client actually does on db:// remote-table connections.

Changes

  • Note that read_consistency_interval applies to all db:// remote-table connections.
  • Replace the version-pinning description with the timestamp-floor model that is now used for read-your-write across writes, checkout_latest, and restore.
  • Mention that the freshness floor is shared across handles to the same table on the same connection.

Context

Triggered by an upstream change that brings read-freshness signaling to the lance-namespace path of db:// connections, so the client behavior described in the docs now holds uniformly for remote tables.

@mintlify

mintlify Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
lancedb-bcbb4faf 🟢 Ready View Preview Jun 17, 2026, 5:39 PM

@prrao87 prrao87 added the needs_new_release Only merge once we release a new version of LanceDB label Jun 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs_new_release Only merge once we release a new version of LanceDB

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants