[codex] clarify docs search indexing and table behavior#253
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR tightens the docs around operational behavior that was previously easy to miss: when indexes are current, how query options compose, what rerankers return, and how table writes interact with versions and schemas.
The root issue is that many API pages described the happy path but left practical edge cases implicit. That can make users unsure about production defaults, async index freshness, mutable table handles, and SDK-specific behavior.
What changed
optimize(), FTS column selection, distance metrics, quantization options, SQL FTS usage, and multivector dimension requirements.Validation
make snippetsgit diff --check