mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-13 15:22:30 +00:00
Jack Ye
fe651ae003
The function catalogue is now real rather than a pointer. Scalar functions are listed by taxonomy -- math, string, unicode, regex, date/time, array, map, struct, crypto, type -- and the names come from what datafusion-functions 54 actually registers, not from what DataFusion documents on main. Aggregate and window pages gain the same treatment. Two things the audit corrected rather than copied. SHOW TABLES does not work. DataFusion implements it over information_schema, which this session does not enable, so it fails at plan time. It was documented as working here, on the SHOW page and in three Manage tables; all four are fixed, and the SQL overview now lists the absence alongside SHOW COLUMNS. Prepared statements are a Flight SQL protocol feature, not a PREPARE statement. A script carrying PREPARE ... AS SELECT will not run, while the same intent expressed through a client will. The new page says so rather than copying DataFusion's syntax. Every section of the Documentation tab that has a SQL counterpart now links to it -- 27 of 76 non-SQL pages, each pointing at the specific statement rather than at the reference index.
90 lines
2.5 KiB
Plaintext
90 lines
2.5 KiB
Plaintext
---
|
|
title: "SHOW"
|
|
sidebarTitle: "Show"
|
|
description: "Listing jobs, functions, materialized views, and the errors a job produced."
|
|
icon: list
|
|
keywords: ["show jobs", "show functions", "show materialized views", "show errors", "show tables"]
|
|
---
|
|
|
|
<Badge color="red">Enterprise</Badge> [SQL runs on a deployment.](/sql)
|
|
|
|
Introspection over objects DataFusion has no concept of. All four are LanceDB
|
|
extensions.
|
|
|
|
<Warning>
|
|
DataFusion's own `SHOW TABLES`, `SHOW COLUMNS` and `SHOW <variable>` are **not
|
|
available**. They are implemented over `information_schema`, which this session
|
|
does not enable, so they fail with
|
|
`"... is not supported unless information_schema is enabled"`.
|
|
|
|
List tables with the SDKs -- `table_names()` / `tableNames()`. For a table's
|
|
columns, use [`DESCRIBE`](/sql/explain#describe).
|
|
</Warning>
|
|
|
|
## SHOW MATERIALIZED VIEWS {#materialized-views}
|
|
|
|
```sql
|
|
SHOW MATERIALIZED VIEWS
|
|
```
|
|
|
|
<Note>
|
|
Cheaper than the SDK equivalent. `list_materialized_views` finds views by
|
|
reading every table's schema, costing one open per table; this asks the server.
|
|
</Note>
|
|
|
|
## SHOW FUNCTIONS {#functions}
|
|
|
|
```sql
|
|
SHOW FUNCTIONS
|
|
```
|
|
|
|
Lists registered [functions](/management/function) and their versions. Since a
|
|
version is immutable and a column pins the version that fills it, this is how
|
|
you find which versions are still in use before dropping one.
|
|
|
|
## SHOW JOBS {#jobs}
|
|
|
|
```sql
|
|
SHOW JOBS
|
|
```
|
|
|
|
Every job the server knows about — id, type, state, creation time. The SQL
|
|
counterpart of `list_jobs`; see [Query and job](/basics/jobs).
|
|
|
|
## SHOW ERRORS {#errors}
|
|
|
|
```sql
|
|
SHOW ERRORS ON <table> [FOR JOB '<job-id>'] [LIMIT <n>]
|
|
```
|
|
|
|
```sql
|
|
SHOW ERRORS ON documents
|
|
SHOW ERRORS ON documents FOR JOB 'job-abc' LIMIT 100
|
|
```
|
|
|
|
Why rows failed. This is the statement to reach for when a
|
|
[refresh](/sql/refresh) reports fewer filled rows than you expected.
|
|
|
|
**Errors and limits**
|
|
|
|
| | |
|
|
| --- | --- |
|
|
| `LIMIT` | must be between 1 and 100,000 |
|
|
| Failed jobs scanned without `FOR JOB` | 32 most recent |
|
|
| Tables the server does not open directly | not supported |
|
|
|
|
Without `FOR JOB` this surveys recent failures and stops at 32 jobs. When the
|
|
listing stops at your `LIMIT`, the message says so — narrow with `FOR JOB`
|
|
rather than raising the limit blindly.
|
|
|
|
## See also {#see-also}
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Management" icon="folder-tree" href="/management">
|
|
The SDK listing calls, per object.
|
|
</Card>
|
|
<Card title="Query and job" icon="hourglass-half" href="/basics/jobs">
|
|
What a job handle exposes beyond these listings.
|
|
</Card>
|
|
</CardGroup>
|