rust/lancedb
1
0
Fork 0
mirror of https://github.com/lancedb/lancedb.git synced 2026-10-13 23:32:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: repair six links to anchors that no longer exist

Browse Source 
Found by `mint broken-links --check-anchors` on the assembled site. Three
point at sections that were renamed or moved: the tag-versioning heading,
the branches comparison table, and the table-creation patterns, which now
live on the Create a table page. Three named sections that no longer exist
and now link to the page they were on.
This commit is contained in:
Brendan Clement
2026-10-05 14:23:23 -07:00
parent 6367f7a0de
commit 8cdff48859
5 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/web/ingestion/index.mdx
+1 -1
View File
@@ -122,4 +122,4 @@ Expected table contents:
| 2 | Bob | 20 |
The example above shows a PyArrow schema. You can just as well create the table using other
table creation patterns (Pandas, Polars, Pydantic, iterators, etc.) -- see [above](#create-a-table-with-data).
table creation patterns (Pandas, Polars, Pydantic, iterators, etc.) -- see [Create a table](/ingestion/create-table#create-a-table-with-data).
docs/web/management/table.mdx
+1 -1
View File
@@ -1140,5 +1140,5 @@ which is when old-version files are removed and disk space is reclaimed.
**Tagged versions are exempt from cleanup.** A version with a tag pointing at it is
retained regardless of age, and its files are not removed by `optimize()`. To make
a tagged version eligible for pruning, [delete the tag](#tag-based-versioning) first.
a tagged version eligible for pruning, [delete the tag](#versioning-tag-based-versioning) first.
</Note>
docs/web/search/vector-search.mdx
+1 -1
View File
@@ -193,7 +193,7 @@ The table below summarizes the behavior of `_distance` in search results based o
</CodeBlock>
</CodeGroup>
For deeper tuning guidance on indexing and performance estimation, see the [vector indexes](/indexing/vector-index/#search-configuration) page,
For deeper tuning guidance on indexing and performance estimation, see the [vector indexes](/indexing/vector-index) page,
For tuning `nprobes`, see below.
### Tuning `approx_mode`
docs/web/sql/ddl/index.mdx
+2 -2
View File
@@ -18,7 +18,7 @@ CREATE INDEX ON documents (title)
SQL `CREATE INDEX` covers **one column** and takes **no user-chosen name** --
the server names it. For a multi-column or explicitly-named index, or to
choose the algorithm, use the SDK's
[`create_index`](/indexing#choosing-an-index).
[`create_index`](/indexing).
</Note>
<Note>
@@ -34,7 +34,7 @@ DROP INDEX documents.title_idx
```
Takes the qualified `table.index` name. Find it with the SDK's
[`list_indices`](/indexing#choosing-an-index) if you created the index without
[`list_indices`](/indexing) if you created the index without
naming it yourself.
## What to read next {#next}
docs/web/tables/branching.mdx
+1 -1
View File
@@ -52,7 +52,7 @@ one to read it. Branches add the missing piece: a *separate, writable* line of
history. Where a tag is a read-only label and `checkout` is a read-only view, a
branch forks from a point in history and then evolves on its own. Creating or
checking out a branch hands you a new table handle whose reads and writes are
scoped to that branch. The [comparison table](#branches-vs-tags-vs-checkout) at
scoped to that branch. The [comparison table](#branches-vs-tags-vs-versions) at
the end of this page lays out when to reach for each.
<Note>