Load Presto data in Python using dltHub

Build a Presto-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

The Presto Client REST API allows users to submit SQL queries to a Presto coordinator, manage query execution, and stream back results. The REST API base URL is http://{coordinator}:{port} and authentication depends on the configured coordinator mechanism such as Kerberos, LDAP, or OAuth 2.0.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Presto data in under 10 minutes.


What data can I load from Presto?

Here are some of the endpoints you can load from Presto:

ResourceEndpointMethodData selectorDescription
query/v1/queryGETReturns information and statistics about queries currently being executed.
query/v1/query/{queryId}GETRetrieves detailed statistics about a specific query.
task/v1/taskGETReturns a list of information for all tasks.
task/v1/task/{taskId}GETRetrieves information about a specific task.
statement/v1/statementPOSTSubmits a statement for execution.
statement/v1/statement/{queryId}/{token}GETRetrieves status updates or next batch of results for a query.

How do I authenticate with the Presto API?

Authentication is handled via the Presto coordinator and depends on the specific security mechanism enabled (e.g., Kerberos, LDAP, OAuth 2.0, or custom authenticators). Requests typically require appropriate headers like X-Presto-User for identity, and security is often configured in the coordinator's config.properties file.

1. Get your credentials

Presto does not have a single unified "API key setup dashboard." Authentication is highly dependent on how your organization has configured the Presto coordinator. Common methods include: 1. Basic Authentication (LDAP/Password file): Obtain your username and password from your organization's Presto administrator. 2. OAuth 2.0: Obtain a client ID, client secret, and token URL from your identity provider or Presto administrator. 3. Kerberos: Ensure your environment is configured with a valid keytab and krb5.conf. Consult your administrator to determine which method is enabled for your specific Presto instance.

2. Add them to .dlt/secrets.toml

[sources.presto_source] username = "your_username" password = "your_password" host = "your_presto_coordinator_host" port = 8080 database = "your_catalog"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Presto API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python presto_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline presto_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset presto_data The duckdb destination used duckdb:/presto.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads /v1/statement and /v1/info from the Presto API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def presto_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://{coordinator}:{port}", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "statement", "endpoint": {"path": "v1/statement"}}, {"name": "task", "endpoint": {"path": "v1/task"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="presto_pipeline", destination="duckdb", dataset_name="presto_data", ) load_info = pipeline.run(presto_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("presto_pipeline").dataset() sessions_df = data.statement.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM presto_data.statement LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("presto_pipeline").dataset() data.statement.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Presto data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Presto?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines