Package: dbt-trino
dbt-trinoIntroductiondbtis 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 usingdbttool is:Can I connect my dbt project to two databases?(see the answeredquestionon the dbt website).TL;DRdbtstands for transformation as inTwithinELTpipelines, it doesn't move data from source to a warehouse.dbt-trinoadapter usesTrinoas 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 thedbt-prestowith adaptations to make it work with Trino.CompatibilityThis dbt plugin has been tested againstTrinoversion435,Starburst Enterpriseversion429-e.0andStarburst Galaxy.Setup & ConfigurationFor information on installing and configuring your profile to authenticate to Trino or Starburst, please refer toStarburst and Trino Setupin the dbt docs.Trino- and Starburst-specific configurationFor Trino- and Starburst-specific configuration, you can refer toStarburst (Trino) configurationson the dbt docs site.ContributingWant to report a bug or request a feature? Let us know onSlackin the#db-presto-trinochannel, or openan issueWant to help us build dbt-trino? Check out theContributing GuideRelease processFirst 5 steps are ONLY relevant for bumpingminorversion:Create1.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 to1.x.latest). Add a new entry in.changes/0.0.0.mdthat points to the newly created latest branch.Runchangie mergeto updateREADME.md. Commit.Bump version ofdbt-tests-adapter. Commit.Merge these 2 commits into the master branch. Add aSkip Changleloglabel to the PR.Continue with the next steps for aminorversion bump. Start from this point for apatchversion bump:RunVersion 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.Rundbt-trino releaseworkflow to releasedbt-trinoto PyPi and GitHub.Backport processSometimes it is necessary to backport some changes to some older versions. In that case, create branch fromx.x.latestbranch. There is ax.x.latestfor each minor version, e.g.1.3.latest. Make a fix and open PR back tox.x.latest. Create changelog bychangie newas ususal, as separate changlog for each minor version is kept on everyx.x.latestbranch.
After merging, to make a release of that version, just follow instructions fromRelease processsection, but run every workflow onx.x.latestbranch.Code of ConductEveryone interacting in the dbt project's codebases, issue trackers, chat rooms, and mailing lists is expected
to follow thePyPA Code of Conduct.