mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-12 23:02:28 +00:00
Jack Ye
c9275e077b
Query and Job were one page because they share the _async convention, but they are different things: a query returns rows and streams them, a job returns an outcome you wait for. Two pages now, query first, each carrying a short pointer to the other rather than the shared framing. Agentic Skills absorbs the agent plugin tutorial, which was a separate page in Use Cases describing the same plugin in more detail -- the two had diverged, with the tutorial carrying the fuller install instructions. It also moves to Getting Started: installing the plugin is something you do before writing anything, not a concept to understand.
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 [Jobs](/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>
|