The trino adapter plugin for dbt (data build tool)
dbt is a data transformation workflow tool that lets teams quickly and collaboratively deploy analytics code, following software engineering best practices like modularity, CI/CD, testing, and documentation. It enables anyone who knows SQL to build production-grade data pipelines.
One frequently asked question in the context of using
dbt tool is:
Can I connect my dbt project to two databases?
(see the answered question on the dbt website).
dbt stands for transformation as in
ELT pipelines, it doesn't move data from source to a warehouse.
dbt-trino adapter uses Trino as a underlying query engine to perform query federation across disperse data sources. Trino connects to multiple and diverse data sources (available connectors) via one dbt connection and process SQL queries at scale. Transformations defined in dbt are passed to Trino which handles these SQL transformation queries and translates them to queries specific to the systems it connects to create tables or views and manipulate data.
This repository represents a fork of the dbt-presto with adaptations to make it work with Trino.
This dbt plugin has been tested against
Starburst Enterprise version
Setup & Configuration
For information on installing and configuring your profile to authenticate to Trino or Starburst, please refer to Starburst and Trino Setup in the dbt docs.
Trino- and Starburst-specific configuration
For Trino- and Starburst-specific configuration, you can refer to Starburst (Trino) configurations on the dbt docs site.
- Want to report a bug or request a feature? Let us know on Slack in the #db-presto-trino channel, or open an issue
- Want to help us build dbt-trino? Check out the Contributing Guide
First 5 steps are ONLY relevant for bumping minor version:
1.x.latestbranch from the latest tag corresponding to current minor version, e.g.
git checkout -b 1.6.latest v1.6.2(when bumping to 1.7). Push branch to remote. This branch will be used for potential backports.
- Create new branch (Do not push below commits to
1.x.latest). Add a new entry in
.changes/0.0.0.mdthat points to the newly created latest branch.
changie mergeto update
- Bump version of
- Merge these 2 commits into the master branch. Add a
Skip Changleloglabel to the PR.
Continue with the next steps for a minor version bump. Start from this point for a patch version bump:
Version Bumpworkflow. The major and minor part of the dbt version are used to associate dbt-trino's version with the dbt version.
- Merge the bump PR. Make sure that test suite pass.
dbt-trino releaseworkflow to release
dbt-trinoto PyPi and GitHub.
Sometimes it is necessary to backport some changes to some older versions. In that case, create branch from
x.x.latest branch. There is a
x.x.latest for each minor version, e.g.
1.3.latest. Make a fix and open PR back to
x.x.latest. Create changelog by
changie new as ususal, as separate changlog for each minor version is kept on every
After merging, to make a release of that version, just follow instructions from Release process section, but run every workflow on
Code of Conduct
Everyone interacting in the dbt project's codebases, issue trackers, chat rooms, and mailing lists is expected to follow the PyPA Code of Conduct.
Release history Release notifications | RSS feed
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Hashes for dbt_trino-1.7.0-py3-none-any.whl