mirror of https://github.com/lancedb/lancedb.git synced 2026-10-13 15:22:30 +00:00

Files

T

Wyatt Alt 5231d37f8d feat: list a table's per-row Function errors from the client (#4208 )

A refresh running under a skip policy records each row it skipped, with
the failing input and the error, but the client could not read that
store: the server exposes it over SQL and, since recently, a REST route.
A user who hit per-row failures still had to open a SQL session.

`Table::function_errors` calls the route. The listing is table-addressed
with optional job and column filters, the same addressing the SQL
surface uses, so the two cannot disagree about what a table's errors
are. The two non-record signals come back as their own fields rather
than as rows: capped-fragment summaries, and whether the listing stopped
at its limit. Local tables refuse rather than answer with an empty list.

Python and Node expose the same call, with the same optional filters.

2026-09-17 05:12:50 -07:00

837 B

Raw Blame History

@lancedb/lancedb • Docs

@lancedb/lancedb / FunctionErrorRecord

Interface: FunctionErrorRecord

One row a Function refresh skipped, as the server recorded it.

Properties

column

column: string;

createdAtMillis

createdAtMillis: number;

errorMessage

errorMessage: string;

errorType

errorType: string;

fragmentId

fragmentId: number;

function

function: string;

functionVersion

functionVersion: string;

jobId

jobId: string;

rowOffset?

optional rowOffset: number;

The row's offset within the fragment; absent when the fragment's detail was capped.

tableVersion

tableVersion: number;

837 B Raw Blame History