mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-13 22:26:53 +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>
30 lines
895 B
Plaintext
30 lines
895 B
Plaintext
---
|
|
title: "Copy"
|
|
sidebarTitle: "Copy"
|
|
description: "COPY ... TO: writing a query result to object storage as files."
|
|
icon: file-export
|
|
keywords: ["copy", "export", "parquet", "sql"]
|
|
---
|
|
|
|
<Warning>
|
|
Recent deployment versions refuse `COPY` over the SQL endpoint with "COPY is not
|
|
supported". On those, export a result by reading it through a Flight SQL client
|
|
or an SDK and writing the files from your application.
|
|
</Warning>
|
|
|
|
<CodeGroup>
|
|
```sql SQL icon="database"
|
|
COPY (SELECT id, title FROM documents) TO 's3://bucket/export/' STORED AS PARQUET
|
|
```
|
|
</CodeGroup>
|
|
|
|
Writes a query result to object storage. This is the export path when the
|
|
consumer is another engine rather than an application: results land as files
|
|
rather than streaming to a client.
|
|
|
|
## What to read next {#next}
|
|
|
|
<Card title="Insert" icon="plus" href="/sql/dml/insert">
|
|
Bringing rows in, rather than exporting them.
|
|
</Card>
|