mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-13 14:16:54 +00:00
Jack YeandClaude Sonnet 5
de95ed3f6d
A broad documentation pass across the areas LanceDB Enterprise and Embedded diverge on most: **Data Curation** -- GPU Function execution, Slurm scheduling (and what Slurm is, for readers new to it), blob late materialization as its own page, joins, aggregation/profiling, sampling, near-duplicate detection, chunking, distributed shuffle, and IVF-partition clustering. **Feature Engineering** -- computed columns and materialized views, restructured to lead with the Function-based path and show the SQL form side by side with Python throughout; a single Auto Refresh page instead of duplicating scheduling details on every refresh page; adaptive execution; checkpointing; GPU and Slurm placement for refresh workers; a Training Cache page for the PyTorch data loader's automatic cache benefit. **Security & Governance** -- an Audit Log reference (schema, access, grants), Secrets promoted to an ordinary catalog object with their own SQL DDL and a vending/rotation guide, and privilege-table fixes verified against the authorization source. **Deployment & Maintenance** -- Horizontal Scaling and OpenTelemetry moved into a real Deployment area; Automated Cleanup folded into Intelligent Auto-Maintenance (every other maintenance decision already lived there); RTE Compaction and Advanced Conflict Resolution documented in depth. **Landing page** -- the Enterprise feature comparison table reorganized (several redundant or stale rows removed, several new areas added), and the "why Enterprise" bullets replaced with ones tied to a concrete page (Performance, Scale, Fault tolerance, Multicloud deployment, Simplify operations) instead of vague promises. Plus a full pass addressing lancedb-gatekeeper's review: a real test-safety bug (a quickstart test could silently overwrite and delete a deployment's own `frames` table), a fabricated SQL statement with no backing implementation, an actual dedup-guarantee bug in `take_row_ids`, and dozens of documentation-accuracy fixes verified against source rather than taken on faith -- each either fixed, or left with an explicit note on why it needs a feature or deployment owner's sign-off instead of being guessed at. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_018PXMCbRH6i5w47TsjeEUMT --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
47 lines
1.6 KiB
Plaintext
47 lines
1.6 KiB
Plaintext
---
|
|
title: "Views"
|
|
sidebarTitle: "View"
|
|
description: "A saved query, evaluated when read."
|
|
icon: eye
|
|
keywords: ["view", "create view", "sql", "catalog"]
|
|
availability:
|
|
embedded: unavailable
|
|
enterprise: available
|
|
---
|
|
|
|
A view saves a query that you can refer to by name. Reading the view executes
|
|
that query against the source tables, using their read-consistency behavior.
|
|
Views do not store a separate copy of the result.
|
|
|
|
It is the counterpart to a
|
|
[materialized view](/management/materialized-view), which stores rows and is
|
|
brought up to date by a refresh. Both are [catalog objects](/basics/catalog)
|
|
defined by a query; choose a materialized view when you need to store and reuse the result.
|
|
|
|
| | View | Materialized view |
|
|
| --- | --- | --- |
|
|
| Stores | the query | the rows |
|
|
| Freshness | follows source-table reads | as of the last refresh |
|
|
| Read cost | executes the saved query | queries the stored result |
|
|
| Write cost | none | a refresh |
|
|
|
|
Views are created in LanceDB Enterprise, either in SQL over the
|
|
[Flight SQL endpoint](/sql#connecting) or with the SDKs' `create_view` /
|
|
`createView`, which send the query to the deployment. Either way, the deployment
|
|
must have views enabled. See [View](/sql/ddl/view) for `CREATE VIEW`,
|
|
`DROP VIEW`, and listing.
|
|
|
|
## Privileges {#privileges}
|
|
|
|
A view's `OWNERSHIP` and `SELECT` are granted through the REST ACL API or
|
|
SQL `GRANT`/`REVOKE`:
|
|
|
|
<CodeGroup>
|
|
```sql SQL icon="database"
|
|
GRANT SELECT ON VIEW dashboard TO ROLE analysts
|
|
```
|
|
</CodeGroup>
|
|
|
|
See [Privileges](/governance/privileges#sql) for the full statement syntax
|
|
and every target it reaches.
|