Skip to content

Update from code changes: document list-element FTS granularity - #340

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

Update from code changes: document list-element FTS granularity#340
mintlify[bot] wants to merge 1 commit into
mainfrom
mintlify/2d9c6ad4

Conversation

@mintlify

@mintlify mintlify Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Summary

LanceDB now lets you choose whether an FTS index treats each table row or each element of the deepest list as one document. Python FTS index config and MatchQuery/PhraseQuery accept a typed row | list_element document_granularity setting, list-element results include a _doc_index column with matching element positions, and nested FTS paths stay public (for example docs.content). In Enterprise, list-element requests require server API version 0.6.0 or later; omitted parameters keep row granularity so existing code is unaffected.

lancedb/lancedb#4050

Changes

  • Added a document_granularity section and parameter-table row to the FTS index page, covering when to use list-element granularity, a Python example, backward compatibility, and the Enterprise server version requirement.
  • Added a list-element document granularity section to the full-text search page, showing the query-time document_granularity parameter on MatchQuery/PhraseQuery, the _doc_index result column, and how the parameter is inferred when omitted.

@mintlify

mintlify Bot commented Aug 26, 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 Aug 26, 2026, 3:33 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants