Repository navigation
Conversation
✅ Deploy Preview for stackable-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
b62eae2 to
3cf836d
Compare
|
I didn't read the content (@adwk67 does), but to me https://docs.stackable.tech/home/stable/trino/usage-guide/connect_to_trino/ would be a good place to have this. |
There was a problem hiding this comment.
This is really helpful - thank you! Just minor things. I think it fits better in the Trino ODBC driver repo, though (users may well need this without SDP, and if they use SDP they will need the ODBC driver anyway), and linked to from our (trino) docs and the postgresql-trino gateway.
| 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. |
There was a problem hiding this comment.
| If the data gateway machine must not run custom connectors or third-party drivers, use the <<postgresql-to-trino-gateway>> instead. | |
| If the data gateway machine should not or cannot run custom connectors or third-party drivers, use the <<postgresql-to-trino-gateway>> instead. |
| == 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. |
There was a problem hiding this comment.
Nit: I think "(the) Microsoft Cloud" is a more natural fit than "Microsoft's cloud"
| |=== | ||
|
|
||
| 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. |
There was a problem hiding this comment.
Is there a word missing here? DML, commands, dialect, or something...
| 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. | |
| The PostgreSQL-to-Trino gateway adds a component in Kubernetes and has to rewrite the PostgreSQL commands that Power BI generates into SQL that Trino parses. |
|
|
||
| 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 |
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. |
There was a problem hiding this comment.
| The data gateway talks to both the Power BI Service and Trino, and passes queries and results between them. | |
| It talks to both the Power BI Service and Trino, and passes queries and results between them. |
Adds a how-to guide under Guides that answers "I run Power BI X, how do I reach Trino on SDP?"
We've had this question a lot this year and it's not easy with so many options.
I hope this clarifies it.