Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
I currently use Power BI Desktop to connect to Apache Hive through a HortonWorks Hive ODBC connection. I pass SQL-like statements to Hive in Power BI to process the statements on the server and then have Hive return the results.
My issue is that returning the data to Power BI is extremely slow. For instance, it takes up to an hour to return a "table" of about 151M records in Power BI. When I use a database management system to query Hive -- like DBeaver, for instance -- I can get around this by running the queries through the Tez engine, with the statement below:
set hive.execution.engine=tez;
More on the Tez engine here.
Running these statements through the Tez engine takes about 1/100th of the time. (BTW: DBeaver connects to Hive through JDBC drivers, which looks like Power BI does not yet support.)
Is there a way to force Power BI to run queries through the Tez engine?
It can be done on the DSN config....go to advanced in your ODBC config...Server Side Properties...Add...put in hive.execution.engine as the key and tez as the value...OK...OK...OK. Worked for me...took an hour long query down to 12 minutes. Not perfect but way more palatable.
Hi,
This is not a solution to your question.
But I am trying to connect to Tez through Hive using Dbeaver, can you please help as you are able to connect.
Thanks in advance!
Manas
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 45 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 69 | |
| 63 | |
| 32 | |
| 31 | |
| 25 |