mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-13 22:26:53 +00:00
## Summary Fixes the problems a page-by-page review of the docs found before launch, after checking each one against the current source and, where noted, the code. The matching fixes for the dataset and Geneva pages, which live in `lancedb/docs`, are in lancedb/docs#402. **Tables** - `integrations/embedding/cohere`: each input-type description was split across two table rows and wrapped in literal quotes (`"`search_document`"`). Now one row per type. - `integrations/embedding/gemini`: removes the same stray quotes from the task-type table. - `integrations/ai/langchain`: the MMR search table's `kwargs` row was missing a cell, so its description sat under Type. - Six reranker pages (answerdotai, cohere, colbert, jina, openai, voyageai): closes the backtick before `_relevance_score`. - `indexing/vector-index`: finishes a cell cut off at "with scalar". - `sql/dql/dedupe`: labels the empty header cell in the resolution table. **Corrections** - `curation/sampling`: sampling works in LanceDB Embedded through the Python SDK, so the page is available in both, with the SQL sections marked Enterprise. - `feature-engineering/index`, `add-computed-column`: automatic refresh is on by default for each computed column and takes effect once a deployment enables its scheduler. `refresh-column` already said so; these two implied it was off. - `indexing/scalar-index`, `indexing/index`: `LABEL_LIST` accelerates `array_has_all`/`array_has_any`; `array_contains_*` doesn't exist. Also merges scalar-index's two "nested fields" sections into one. - `integrations/embedding/ibm`: lists the four current models from `CURRENT_MODELS` (it listed a deprecated one) and explains that the default stays a legacy ID so existing tables reload with their model. - `integrations/reranking/openai`: the class is `OpenaiReranker`, not `OpenAI()`. - `integrations/ai/synthetic-data-kit`: the CLI is `synthetic-data-kit` throughout, each step runs one command, each step passes the file it writes to the next, and `save-as` uses `-f`/`-o`. - `integrations/data/dlt`: `secrets.toml` defines `api_token`, which the pipeline reads, and the run command runs the file the page creates. - `search/vector-search`: the multivector walkthrough connected to Enterprise in step 1 and a local path in step 2. It now runs locally throughout, with a note on connecting to Enterprise, and is renamed so it doesn't read as a duplicate of the short section above. **Structure and wording** - `integrations/embedding/nvidia`: adds headings, and drops test-suite details aimed at contributors. - `integrations/ai/genkit`: makes the retrieval test a real heading and describes the query step. - `integrations/data/voxel51`: replaces a raw MkDocs `!!! note` with a `<Note>`. - `sql/ddl/table`, `sql/ddl/job`: "Errors and limits" is a real heading, not bold text. - `curation/windowing`: sidebar title matches the curation overview ("Rank and Deduplicate"). - `deployment/storage`, `basics/agentic-skills`: fixes a garbled sentence and a stale reference to the quickstart. **Checked:** no new Vale alerts on the changed pages. Assembled together with lancedb/docs#402, the site passes `mint validate` and `mint broken-links --check-anchors --check-redirects`. Every changed page was reviewed in a local preview. 🤖 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_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:**
|
|
```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 rest_api_pipeline.py
|
|
```
|
|
|
|
For more information and advanced usage of dlt's LanceDB integration, read [the dlt documentation](https://dlthub.com/docs/dlt-ecosystem/destinations/lancedb).
|