Load lakeFS data to DuckDB

lakeFS is a version control system for data lakes that provides a REST API for managing branches, commits, and data operations. Everything needed to build a working lakeFS → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your lakeFS to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from lakeFS to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the lakeFS API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

lakeFS API at a glance

These values come from the lakeFS API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the lakeFS API?

lakeFS primarily uses HTTP Basic Authentication, requiring an 'Authorization' header containing 'Basic ' followed by a base64-encoded string of 'access_key_id:secret_access_key'. Alternatively, it supports JWT Bearer tokens passed in the 'Authorization' header as 'Bearer '.

1. Get your credentials

1. Open the lakeFS Web UI in your browser (typically http://localhost:8000).
2. On first use, navigate to the setup page to create an initial administrator user.
3. Once logged in, navigate to the Administration section in the sidebar.
4. Select Users to manage user accounts.
5. Create a new user or select an existing one to generate or view credentials.
6. Copy and save the Access Key ID and Secret Access Key immediately upon generation, as the secret key will not be displayed again.

2. Add them to .dlt/secrets.toml

Copy
[sources.lakefs_source]
access_key_id = "AKIA..."
secret_access_key = "..."
server_endpoint_url = "http://localhost:8000"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What lakeFS data can I load into DuckDB?

These are the lakeFS endpoints dlt can load into DuckDB:

---

How do I load only new lakeFS records?

lakeFS exposes after on repositories, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "repositories", "endpoint": {
    "path": "repositories",
    "data_selector": "results",
    "incremental": {"cursor_path": "after", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated lakeFS pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /auth/users/{userId}/credentials and /auth/login from the lakeFS API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def lakefs_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://<your-lakefs-instance>/api/v1",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "repositories", "endpoint": {"path": "repositories", "data_selector": "results"}},
            {"name": "branches", "endpoint": {"path": "repositories/{repository}/branches", "data_selector": "results"}}
        ],
    }
    yield from rest_api_resources(config)


def load_lakefs_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="lakefs_pipeline",
        destination="duckdb",
        dataset_name="lakefs_data",
    )
    load_info = pipeline.run(lakefs_source())
    print(load_info)


if __name__ == "__main__":
    load_lakefs_to_duckdb()

Run it with python lakefs_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query lakeFS data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("lakefs_pipeline").dataset()
df = data.repositories.df()
print(df.head())

SQL:

Copy
SELECT * FROM lakefs_data.repositories LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the lakeFS to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw lakeFS loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load lakeFS data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack