Conversation
|
ACTION NEEDED The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification. For details on the error please inspect the "PR Title Check" action. |
PR Review: docs: add FTS docsGood documentation addition covering FTS capabilities in Lance. The content is well-organized and the code examples are consistent with the current Python API. P1: Documentation Link ErrorIn Check out **[Full-text Search](../quickstart/versioning.md)**, where we show...This should link to Check out **[Full-text Search](../quickstart/full-text-search.md)**, where we show...The API examples appear accurate based on current implementation in |
BubbleCal
left a comment
BubbleCal
left a comment
There was a problem hiding this comment.
it's worth mentioning fuzzy search
LGTM overall
|
|
||
| ### Index Maintenance | ||
|
|
||
| As your data evolves over time, it's important to periodically rebuild your indexes to maintain optimal search performance. When you add, modify, or delete documents, the existing index may become less efficient. Consider scheduling regular index rebuilds, especially for datasets with frequent updates. |
There was a problem hiding this comment.
How does one update the existing FTS index in Lance? @BubbleCal
|
Good point about fuzzy search! Will add. |
|
Give me till end of day to finalize the fuzzy search doc and will add that in. Thanks for reviewing! |
3 participants
We lack docs for how to create and query an FTS index in Lance. This PR adds detailed docs, based on the latest v1.0.4
pylanceAPI. All code snippets have been tested with the latest stable release and I gave it another pass with GPT 5.2 to ensure accuracy per the latest Rust code in tokenizer.rs.