rust/lancedb
1
0
Fork 0
mirror of https://github.com/lancedb/lancedb.git synced 2026-09-04 20:48:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

update

Browse Source
This commit is contained in:
Dan Tasse
2026-08-25 16:39:56 -04:00
parent ac2956c1e2
commit e7633686f6
4 changed files with 16 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/src/js/classes/Table.md
+4 -3
View File
@@ -1296,9 +1296,10 @@ The following keys are treated specially, by convention, and should be
used when appropriate:
- `lancedb:description`: for a human-readable description of a field.
- `lancedb:tag:(tag_name)`: for a user-defined key-value tag.
- `lancedb:logical_column`: for a column grouping; e.g. `feature_v1` and
`feature_v2` might be in the same logical_column.
- `lancedb:tag:<name>`: for a user-defined key-value tag, where the suffix
names the tag category; e.g. `lancedb:tag:model: "clip"`.
- `lancedb:logical-column`: for a column grouping; e.g. `feature_v1` and
`feature_v2` might be in the same logical column.
- `lancedb:status`: for status options (`production`, `candidate`,
`deprecated`, `archived`) to designate the current life cycle state of
this column.
nodejs/lancedb/table.ts
+4 -3
View File
@@ -633,9 +633,10 @@ export abstract class Table {
* used when appropriate:
*
* - `lancedb:description`: for a human-readable description of a field.
* - `lancedb:tag:(tag_name)`: for a user-defined key-value tag.
* - `lancedb:logical_column`: for a column grouping; e.g. `feature_v1` and
* `feature_v2` might be in the same logical_column.
* - `lancedb:tag:<name>`: for a user-defined key-value tag, where the suffix
* names the tag category; e.g. `lancedb:tag:model: "clip"`.
* - `lancedb:logical-column`: for a column grouping; e.g. `feature_v1` and
* `feature_v2` might be in the same logical column.
* - `lancedb:status`: for status options (`production`, `candidate`,
* `deprecated`, `archived`) to designate the current life cycle state of
* this column.
python/python/lancedb/table.py
+4 -3
View File
@@ -2131,9 +2131,10 @@ class Table(ABC):
be used when appropriate:
- "lancedb:description": for a human-readable description of a field.
- "lancedb:tag:(tag_name)" for a user-defined key-value tag.
- "lancedb:logical_column" for a column grouping; e.g. "feature_v1"
and "feature_v2" might be in the same logical_column.
- ``"lancedb:tag:<name>"`` for a user-defined key-value tag, where the
suffix names the tag category; e.g. "lancedb:tag:model": "clip".
- "lancedb:logical-column" for a column grouping; e.g. "feature_v1"
and "feature_v2" might be in the same logical column.
- "lancedb:status" for status options ("production", "candidate",
"deprecated", "archived") to designate the current life cycle
state of this column.
rust/lancedb/src/table.rs
+4 -3
View File
@@ -1762,9 +1762,10 @@ impl Table {
/// used when appropriate:
///
/// - `lancedb:description`: for a human-readable description of a field.
/// - `lancedb:tag:(tag_name)`: for a user-defined key-value tag.
/// - `lancedb:logical_column`: for a column grouping; e.g. `feature_v1` and
/// `feature_v2` might be in the same logical_column.
/// - `lancedb:tag:<name>`: for a user-defined key-value tag, where the suffix
/// names the tag category; e.g. `lancedb:tag:model: "clip"`.
/// - `lancedb:logical-column`: for a column grouping; e.g. `feature_v1` and
/// `feature_v2` might be in the same logical column.
/// - `lancedb:status`: for status options (`production`, `candidate`,
/// `deprecated`, `archived`) to designate the current life cycle state of
/// this column.