mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-13 22:26:53 +00:00
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>
108 lines
5.8 KiB
Plaintext
108 lines
5.8 KiB
Plaintext
---
|
|
title: "dlt"
|
|
sidebarTitle: "DLT"
|
|
|
|
---
|
|
|
|
import {
|
|
PyPlatformsDltAdapterImport,
|
|
PyPlatformsDltAdapterUsage,
|
|
PyPlatformsDltPipeline,
|
|
} from '/snippets/integrations.mdx';
|
|
|
|
[dlt](https://dlthub.com/docs/intro) is an open-source library that you can add to your Python scripts to load data from various and often messy data sources into well-structured, live datasets. dlt's [integration with LanceDB](https://dlthub.com/docs/dlt-ecosystem/destinations/lancedb) lets you ingest data from any source (databases, APIs, CSVs, dataframes, JSONs, and more) into LanceDB with a few lines of simple python code. The integration enables automatic normalization of nested data, schema inference, incremental loading and embedding the data. dlt also has integrations with several other tools like dbt, airflow, dagster etc. that can be inserted into your LanceDB workflow.
|
|
|
|
## How to ingest data into LanceDB {#how-to-ingest-data-into-lancedb}
|
|
|
|
In this example, we will be fetching movie information from the [Open Movie Database (OMDb) API](https://www.omdbapi.com/) and loading it into a local LanceDB instance. To implement it, you will need an API key for the OMDb API (which can be created freely [here](https://www.omdbapi.com/apikey.aspx)).
|
|
|
|
1. **Install `dlt` with LanceDB extras:**
|
|
<CodeGroup>
|
|
```bash Bash icon="terminal"
|
|
pip install dlt[lancedb]
|
|
```
|
|
</CodeGroup>
|
|
|
|
2. **Inside an empty directory, initialize a `dlt` project with:**
|
|
<CodeGroup>
|
|
```bash Bash icon="terminal"
|
|
dlt init rest_api lancedb
|
|
```
|
|
</CodeGroup>
|
|
This will add all the files necessary to create a `dlt` pipeline that can ingest data from any REST API (ex: OMDb API) and load into LanceDB.
|
|
```text
|
|
├── .dlt
|
|
│ ├── config.toml
|
|
│ └── secrets.toml
|
|
├── rest_api
|
|
├── rest_api_pipeline.py
|
|
└── requirements.txt
|
|
```
|
|
|
|
dlt has a list of pre-built [sources](https://dlthub.com/docs/dlt-ecosystem/verified-sources/) like [SQL databases](https://dlthub.com/docs/dlt-ecosystem/verified-sources/sql_database), [REST APIs](https://dlthub.com/docs/dlt-ecosystem/verified-sources/rest_api), [Google Sheets](https://dlthub.com/docs/dlt-ecosystem/verified-sources/google_sheets), [Notion](https://dlthub.com/docs/dlt-ecosystem/verified-sources/notion) etc., that can be used out-of-the-box by running `dlt init <source_name> lancedb`. Since dlt is a python library, it is also very easy to modify these pre-built sources or to write your own custom source from scratch.
|
|
|
|
|
|
3. **Specify necessary credentials and/or embedding model details:**
|
|
|
|
To fetch data from the OMDb API, you will need to pass a valid API key into your pipeline. Depending on whether you're using LanceDB Embedded or LanceDB Enterprise, you also may need to provide the necessary credentials to connect to the LanceDB instance. These can be pasted inside `.dlt/secrets.toml`.
|
|
|
|
dlt's LanceDB integration also allows you to automatically embed the data during ingestion. Depending on the embedding model chosen, you may need to paste the necessary credentials inside `.dlt/secrets.toml`:
|
|
```toml
|
|
[sources.rest_api]
|
|
api_token = "api_token" # Enter the API key for the OMDb API
|
|
|
|
[destination.lancedb]
|
|
embedding_model_provider = "sentence-transformers"
|
|
embedding_model = "all-MiniLM-L6-v2"
|
|
[destination.lancedb.credentials]
|
|
uri = ".lancedb"
|
|
api_key = "api_key" # API key to connect to LanceDB Enterprise. Leave out if you are using LanceDB Embedded.
|
|
embedding_model_provider_api_key = "embedding_model_provider_api_key" # Not needed for providers that don't need authentication (ollama, sentence-transformers).
|
|
```
|
|
See [here](https://dlthub.com/docs/dlt-ecosystem/destinations/lancedb#configure-the-destination) for more information and for a list of available models and model providers.
|
|
|
|
|
|
4. **Write the pipeline code inside `rest_api_pipeline.py`:**
|
|
|
|
The following code shows how you can configure dlt's REST API source to connect to the [OMDb API](https://www.omdbapi.com/), fetch all movies with the word "godzilla" in the title, and load it into a LanceDB table. The REST API source allows you to pull data from any API with minimal code, to learn more read the [dlt docs](https://dlthub.com/docs/dlt-ecosystem/verified-sources/rest_api).
|
|
|
|
<CodeBlock filename="Python" language="Python" icon="python">
|
|
{PyPlatformsDltPipeline}
|
|
</CodeBlock>
|
|
|
|
The script above will ingest the data into LanceDB as it is, i.e. without creating any embeddings. If we want to embed one of the fields (for example, `"Title"` that contains the movie titles), then we will use dlt's `lancedb_adapter` and modify the script as follows:
|
|
|
|
- Add the following import statement:
|
|
<CodeBlock filename="Python" language="Python" icon="python">
|
|
{PyPlatformsDltAdapterImport}
|
|
</CodeBlock>
|
|
- Modify the pipeline run like this:
|
|
<CodeBlock filename="Python" language="Python" icon="python">
|
|
{PyPlatformsDltAdapterUsage}
|
|
</CodeBlock>
|
|
This will use the embedding model specified inside `.dlt/secrets.toml` to embed the field `"Title"`.
|
|
|
|
5. **Install necessary dependencies:**
|
|
<CodeGroup>
|
|
```bash Bash icon="terminal"
|
|
pip install -r requirements.txt
|
|
```
|
|
</CodeGroup>
|
|
|
|
Note: You may need to install the dependencies for your embedding models separately.
|
|
<CodeGroup>
|
|
```bash Bash icon="terminal"
|
|
pip install sentence-transformers
|
|
```
|
|
</CodeGroup>
|
|
|
|
6. **Run the pipeline:**
|
|
Finally, running the following command will ingest the data into your LanceDB instance.
|
|
<CodeGroup>
|
|
```bash Bash icon="terminal"
|
|
python rest_api_pipeline.py
|
|
```
|
|
</CodeGroup>
|
|
|
|
For more information and advanced usage of dlt's LanceDB integration, read [the dlt documentation](https://dlthub.com/docs/dlt-ecosystem/destinations/lancedb).
|