Repository navigation
docs: Add a guide for connecting Power BI to Trino #963
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,137 @@ | ||||||
| = Connecting Power BI to Trino | ||||||
| :description: Connect Power BI Desktop, the Power BI Service and Power BI Report Server to Trino on the Stackable Data Platform, using the Stackable ODBC driver or the Stackable PostgreSQL-to-Trino gateway. | ||||||
| :odbc-repo: https://github.com/stackabletech/stackable-odbc-trino | ||||||
| :odbc-releases: https://github.com/stackabletech/stackable-odbc-trino/releases | ||||||
| :pg-gateway-repo: https://github.com/stackabletech/postgresql-trino-gateway | ||||||
| :pg-gateway-chart: https://github.com/stackabletech/postgresql-trino-gateway/tree/main/deploy/helm/postgresql-trino-gateway | ||||||
| :ms-gateway-install: https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-install | ||||||
| :ms-gateway-custom: https://learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-custom-connectors | ||||||
| :ms-gateway-sso: https://learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-sso-overview | ||||||
| :ms-rs-sources: https://learn.microsoft.com/en-us/power-bi/report-server/data-sources | ||||||
| :ms-connector-announcement: https://community.fabric.microsoft.com/blog/fbc_pbiupdatesblog/empowering-our-customers-to-shape-the-future-of-data-connectivity-in-power-bi-an/5174038 | ||||||
|
|
||||||
| This guide shows how each Microsoft Power BI product connects to Trino on the Stackable Data Platform (SDP). | ||||||
|
|
||||||
| There are two ways to connect them: | ||||||
|
|
||||||
| * the {odbc-repo}[Stackable ODBC driver for Trino{external-link-icon}^], which ships with a Power Query connector that adds *Stackable Trino* to the *Get Data* dialog, and | ||||||
| * the {pg-gateway-repo}[Stackable PostgreSQL-to-Trino gateway{external-link-icon}^], which runs in Kubernetes next to Trino and accepts PostgreSQL connections, so Power BI's built-in PostgreSQL connector can query Trino. | ||||||
|
|
||||||
| [IMPORTANT] | ||||||
| ==== | ||||||
| Both are open source, and neither is part of SDP. | ||||||
| Stackable support doesn't cover them. | ||||||
| If you need commercial support for either of them, https://stackable.tech/en/contact[contact us{external-link-icon}^]. | ||||||
| ==== | ||||||
|
|
||||||
| Which one you need, and where you install it, depends on the Power BI product you run. | ||||||
|
|
||||||
| image::connecting-power-bi/where-each-piece-runs.svg["Where each piece runs: Microsoft's cloud, the customer's network and SDP on Kubernetes"] | ||||||
|
|
||||||
| == Choose a route | ||||||
|
|
||||||
| [NOTE] | ||||||
| ==== | ||||||
| Power BI loads data in one of two modes. | ||||||
| Import copies the data into the Power BI model at each refresh, and reports query that copy. | ||||||
| DirectQuery leaves the data in Trino and sends a query to Trino for every report interaction. | ||||||
| ==== | ||||||
|
|
||||||
| [cols="2,3,3,4"] | ||||||
| |=== | ||||||
| |You run |Import |DirectQuery |You install | ||||||
|
|
||||||
| |Power BI Desktop | ||||||
| |ODBC driver (recommended) or PostgreSQL-to-Trino gateway | ||||||
| |ODBC driver (recommended) or PostgreSQL-to-Trino gateway | ||||||
| a|Either | ||||||
|
|
||||||
| * the ODBC driver and connector on the analyst's PC, or | ||||||
| * the PostgreSQL-to-Trino gateway in Kubernetes | ||||||
|
|
||||||
| |Power BI Service (cloud) | ||||||
| |ODBC driver (recommended) or PostgreSQL-to-Trino gateway | ||||||
| |ODBC driver (recommended) or PostgreSQL-to-Trino gateway | ||||||
| a|Microsoft's on-premises data gateway on a Windows machine, and either | ||||||
|
|
||||||
| * the ODBC driver and connector on that machine, or | ||||||
| * the PostgreSQL-to-Trino gateway in Kubernetes | ||||||
|
|
||||||
| |Power BI Report Server | ||||||
| |ODBC driver or PostgreSQL-to-Trino gateway | ||||||
| |PostgreSQL-to-Trino gateway | ||||||
| a|Either | ||||||
|
|
||||||
| * the ODBC driver on the Report Server, or | ||||||
| * the PostgreSQL-to-Trino gateway in Kubernetes | ||||||
| |=== | ||||||
|
|
||||||
| Where both routes work, the ODBC driver is the recommended one, because the connector sends Trino SQL straight to Trino. | ||||||
| The PostgreSQL-to-Trino gateway adds a component in Kubernetes and has to rewrite the PostgreSQL that Power BI generates into SQL that Trino parses. | ||||||
|
|
||||||
| Every route needs Trino reachable from the Windows machine that runs the Power BI component: the analyst's PC, the data gateway machine or the Report Server. | ||||||
| xref:trino:usage-guide/connect_to_trino.adoc[] covers the Trino side: endpoints, TLS and authentication. | ||||||
|
|
||||||
| == Power BI Desktop | ||||||
|
|
||||||
| Power BI Desktop is a Windows application on the analyst's PC. | ||||||
| It queries Trino directly from that PC, without Microsoft's cloud in the path. | ||||||
|
Member
There was a problem hiding this comment. Nit: I think "(the) Microsoft Cloud" is a more natural fit than "Microsoft's cloud" |
||||||
|
|
||||||
| . Download the Windows archive from the {odbc-releases}[releases page{external-link-icon}^], unzip it and run `install.bat` as administrator. | ||||||
| . Copy `StackableTrinoODBC-<version>.mez` into `%USERPROFILE%\Documents\Power BI Desktop\Custom Connectors\`. | ||||||
| . In *File > Options and settings > Options > Security*, allow any extension to load, then restart Power BI Desktop. | ||||||
| . Select *Get Data*, choose *Stackable Trino*, and enter the Trino coordinator's server, port and catalog. | ||||||
|
|
||||||
| Each analyst connects with their own Trino credentials, or with Trino's browser login when *External authentication* is enabled in the connector's advanced options. | ||||||
|
|
||||||
| To use the PostgreSQL-to-Trino gateway instead, deploy it as described in <<postgresql-to-trino-gateway>> and connect with Power BI's built-in *PostgreSQL database* connector. | ||||||
|
|
||||||
| == Power BI Service | ||||||
|
Member
There was a problem hiding this comment. We should test PowerBI service soon. PBI is not included in our Azure subscription, though. Prices: https://www.microsoft.com/en/power-platform/products/power-bi/pricing |
||||||
|
|
||||||
| The Power BI Service runs in Microsoft's cloud and reaches Trino only through Microsoft's on-premises data gateway. | ||||||
| The data gateway is a Windows service that you install on a machine that can reach Trino. | ||||||
| The data gateway talks to both the Power BI Service and Trino, and passes queries and results between them. | ||||||
|
Member
There was a problem hiding this comment.
Suggested change
|
||||||
|
|
||||||
| . {ms-gateway-install}[Install the on-premises data gateway{external-link-icon}^] on a Windows machine that can reach Trino. | ||||||
| . Install the Stackable ODBC driver on that machine, as for Power BI Desktop. | ||||||
| . Copy the `.mez` connector into a folder that the data gateway's service account can read, and select that folder under *Connectors* in the data gateway app. | ||||||
| . In the Power BI Service, enable custom connectors in the gateway cluster's settings and add a *Stackable Trino* data source with the credential Trino should see. | ||||||
|
|
||||||
| {ms-gateway-custom}[Use custom data connectors with the on-premises data gateway{external-link-icon}^] covers the Microsoft side of steps 3 and 4. | ||||||
|
|
||||||
| Every viewer's queries run as the data source's stored credential, so Trino's access rules see one user for all viewers. | ||||||
| Per-user restrictions have to be Power BI row-level security. | ||||||
| A DirectQuery model can use only one custom-connector data source, and Kerberos with Windows authentication isn't available for custom connectors through the data gateway. | ||||||
|
|
||||||
| If the data gateway machine must not run custom connectors or third-party drivers, use the <<postgresql-to-trino-gateway>> instead. | ||||||
|
Member
There was a problem hiding this comment.
Suggested change
|
||||||
| The data gateway's built-in PostgreSQL connector then needs no Stackable software on that machine. | ||||||
|
|
||||||
| [WARNING] | ||||||
| .Single sign-on isn't available | ||||||
| ==== | ||||||
| Power BI's {ms-gateway-sso}[single sign-on through the data gateway{external-link-icon}^], which runs each viewer's queries under their own identity, isn't available for Trino. | ||||||
| Microsoft enables it per connector in the Power BI Service and doesn't enable it for custom connectors such as *Stackable Trino*. | ||||||
| Since September 2025, Microsoft builds new connectors itself and no longer certifies connectors from partners ({ms-connector-announcement}[announcement{external-link-icon}^]). | ||||||
| ==== | ||||||
|
|
||||||
| == Power BI Report Server | ||||||
|
|
||||||
| Power BI Report Server is server software on your own Windows server. | ||||||
| It queries Trino without Microsoft's cloud in the path. | ||||||
| It allows DirectQuery only for a {ms-rs-sources}[short list of data sources{external-link-icon}^] that includes PostgreSQL but not ODBC, and it doesn't refresh reports that use custom connectors. | ||||||
|
|
||||||
| That's why Stackable built the <<postgresql-to-trino-gateway>>: Report Server sees a PostgreSQL database and gets DirectQuery against Trino. | ||||||
|
|
||||||
| * For import and DirectQuery, deploy the <<postgresql-to-trino-gateway>> and use the built-in *PostgreSQL database* connector with user and password. | ||||||
| * For import only, install the Stackable ODBC driver on the Report Server, create a DSN for Trino with *ODBC Data Sources (64-bit)*, and use the built-in *ODBC* connector. | ||||||
|
|
||||||
| [#postgresql-to-trino-gateway] | ||||||
| == PostgreSQL-to-Trino gateway | ||||||
|
|
||||||
| The gateway runs in Kubernetes next to Trino and accepts PostgreSQL connections on port 5432. | ||||||
| It forwards queries to Trino and returns the results over the PostgreSQL protocol. | ||||||
| Most queries pass through unchanged, and the gateway rewrites the PostgreSQL constructs that Trino doesn't parse, such as `::` casts and `ILIKE`. | ||||||
| Install its Helm chart with the Trino coordinator's host and port, and make its Service reachable from the machine that runs the Power BI component. | ||||||
| {pg-gateway-chart}[The chart's README{external-link-icon}^] covers authentication and TLS. | ||||||
|
|
||||||
| The gateway runs as a single replica, because a PostgreSQL cancel request has to reach the replica that holds the connection. | ||||||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a word missing here? DML, commands, dialect, or something...