The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Hello,
I am relatively new to Power BI and am wondering why my native query doesn't seem to work. I am connecting to Qubole Presto via ODBC. I wrote a query which does some some transformations to a particular field to create a new field. Here is a snippet:
SELECT
case when url is not null then
substr(url,1,length(url)-strpos(reverse(url), '/')) else NULL end as baseurl, url,...
When I run the query in Power Query, it does return the added 'baseurl' column, but none of the string transformations applied...basically it just returns 'url' in that field. I ran this in Presto and it worked fine. Does Power Query not recognize the string functions?
Solved! Go to Solution.
Hello,
I am able to connect to Presto. I had to rework my query. Instead of using some of the string functions I used regex instead..that seemed to work. I originally thought that it was my case statements that could be breaking it but I kept those in, and they still work. Perhaps it was one of the string functions.
Thanks!
Hi @Anonymous
Please delete the sql statement and make a test if you could connect to Qubole Presto via ODBC in power bi desktop.
If it can connect successfully, please open the advanced editor in Edit queries and share the code here for further analysis.
If not, please refer to the followings:
https://www.simba.com/webinar/connect-presto-bi-application/
https://www.simba.com/products/Presto/doc/ODBC_InstallGuide/win/content/odbc/dr/intro.htm
https://docs.microsoft.com/en-us/power-bi/desktop-connect-using-generic-interfaces
Besides, which is the "url", is it the connnection string or any fields from data sources?
Best Regards
Maggie
Community Support Team _ Maggie Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello,
I am able to connect to Presto. I had to rework my query. Instead of using some of the string functions I used regex instead..that seemed to work. I originally thought that it was my case statements that could be breaking it but I kept those in, and they still work. Perhaps it was one of the string functions.
Thanks!