Files
lancedb/docs/src/js/interfaces/IndexStatistics.md
T
Will Jones 09b1bbc12a refactor!: drop unused loss field from IndexStatistics (#3496)
BREAKING CHANGE: direct Rust users lose the `IndexStatistics::loss`
field. Python and Node.js consumers are unaffected in practice for
remote tables (the value was always `None`/absent), but the attribute is
gone for local tables too.

`IndexStatistics::loss` was local-only — LanceDB Cloud never returned
it, so
`RemoteTable::index_stats` always set `loss: None`. It's vestigial; this
removes it.

- Remove `loss` from `IndexStatistics` and the internal `IndexMetadata`
in `rust/lancedb/src/index.rs`, plus the summing logic in
`NativeTable::index_stats`.
- Drop `loss` from the Python and Node.js bindings (and their
tests/docs).

Fixes #3493

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-05 07:52:40 -07:00

60 lines
757 B
Markdown

[**@lancedb/lancedb**](../README.md) • **Docs**
***
[@lancedb/lancedb](../globals.md) / IndexStatistics
# Interface: IndexStatistics
## Properties
### distanceType?
```ts
optional distanceType: string;
```
The type of the distance function used by the index. This is only
present for vector indices. Scalar and full text search indices do
not have a distance function.
***
### indexType
```ts
indexType: string;
```
The type of the index
***
### numIndexedRows
```ts
numIndexedRows: number;
```
The number of rows indexed by the index
***
### numIndices?
```ts
optional numIndices: number;
```
The number of parts this index is split into.
***
### numUnindexedRows
```ts
numUnindexedRows: number;
```
The number of rows not indexed