mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-30 15:26:52 +00:00
## Summary Adopts the product terminology guide across the docs site pages, SDK docstrings and error messages. "LanceDB OSS" and local mode become **LanceDB Embedded**. "Remote" as the execution model becomes **LanceDB Distributed**, which LanceDB Enterprise provides. Where free vs paid is the point, pages contrast "LanceDB Embedded (open source)" with "LanceDB Enterprise". This is a first trial of the Embedded name, so reviewers can judge it in context. - **Embedded vs Distributed** for where execution runs (`optimize()`, consistency, branching, maintenance). Main pages define it once: "LanceDB Enterprise runs LanceDB Distributed: …" - **LanceDB Cloud** is kept only for legacy-Cloud specifics (`db://` region, the brute-force KNN limit) and marked legacy. "Cloud and Enterprise" becomes Enterprise or Distributed. - **Plan executor** becomes "executor" or the fleet name. - **Error messages** change, e.g. `optimize is not supported for remote tables.` → `... in LanceDB Distributed.` Tests that match on them are updated. - **Vale rules** (`EmbeddedName`, `OSSProduct`, `RemoteExecution`, `DistributedEnterprise`, `LegacyCloud`, `InternalNames`) enforce the terms in prose. Unchanged: identifiers (`availability.oss`, the `remote` module and feature, `RemoteTable`, `db://`), heading anchors, internal code comments, and Geneva. ## Evidence - Rust lib tests for the changed messages and the Python tests in `test_remote_db.py`, `test_materialized_views.py` and `test_table.py` pass locally. - Not run locally: - The Node tests: `remote.test.ts` and `table.test.ts` have updated assertions. - Vale. - The `experimental_functions`-marked materialized-view tests. - `docs/src` API reference was hand-edited to match the docstrings rather than regenerated. ## Merge Risk **Door:** two-way; prose and message text only. **Blast Radius:** `docs`, `error-messages`: callers matching on old error strings would break. Companion PRs: lancedb/docs (assembler labels, STYLE.md) and sophon (Enterprise pages). 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
98 lines
5.5 KiB
Plaintext
98 lines
5.5 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:**
|
|
```sh
|
|
pip install dlt[lancedb]
|
|
```
|
|
|
|
2. **Inside an empty directory, initialize a `dlt` project with:**
|
|
```sh
|
|
dlt init rest_api lancedb
|
|
```
|
|
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_key = "api_key" # 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:**
|
|
```sh
|
|
pip install -r requirements.txt
|
|
```
|
|
|
|
Note: You may need to install the dependencies for your embedding models separately.
|
|
```sh
|
|
pip install sentence-transformers
|
|
```
|
|
|
|
6. **Run the pipeline:**
|
|
Finally, running the following command will ingest the data into your LanceDB instance.
|
|
```sh
|
|
python custom_source.py
|
|
```
|
|
|
|
For more information and advanced usage of dlt's LanceDB integration, read [the dlt documentation](https://dlthub.com/docs/dlt-ecosystem/destinations/lancedb).
|