Forum Discussion

CansuT's avatar
CansuT
Regular Visitor
1 year ago
Solved

DataSource.Error: ADBC: UnknownError while running a query with left join

I am getting this error after adding a data source that is a simple query that joins a view and a table from google bigquery. I tried adding each one of the sources (the view and the table) seperatel...
Need Help
  • vojtechsima's avatar
    vojtechsima
    1 year ago

    Hello, CansuT ,

    You can try double-checking the selection to ensure that there are no duplicate column names, so use aliases for every column. Also, if possible, wrap your request inside Value.NativeQuery (with EnableFolding=true) function that should help with ensuring it folds back to source. Alternatively, if you have non-common data types for Power BI, you can try to normalise them in the select itself.

     

    Native Query syntax:

    Value.NativeQuery(GoogleBigQuery.Database(...), SqlAsText, null, [EnableFolding = false])
vojtechsima's avatar
vojtechsima
Super User
1 year ago

Hello, CansuT ,

You can try double-checking the selection to ensure that there are no duplicate column names, so use aliases for every column. Also, if possible, wrap your request inside Value.NativeQuery (with EnableFolding=true) function that should help with ensuring it folds back to source. Alternatively, if you have non-common data types for Power BI, you can try to normalise them in the select itself.

 

Native Query syntax:

Value.NativeQuery(GoogleBigQuery.Database(...), SqlAsText, null, [EnableFolding = false])
  • CansuT's avatar
    CansuT
    Regular Visitor
    1 year ago

    There weren't any duplicate/ambigious column names but using aliases everywhere solved this issue. 
    It used to be okay to not use aliases when there the column only existed in one of the tables. Has there been a change on Google's side that led to this issue now?

  • danzrust's avatar
    danzrust
    Helper IV
    11 months ago

    I had the same error. My mistake that I had two columns with the same name.


    However, the ADBC implementation has extremely poor messaging. Previous implementation would you show the errors from BQ API directly in PowerBI. The new ADBC just says "UnknownError...". Very unhelpful. 

     

    I just edited the source to = GoogleBigQuery.Database([BillingProject="abc"]) and completely removed new Implemetnation=2.0. That way I was able to read the error from BQ API.

    • Cedric_B's avatar
      Cedric_B
      New Member
      11 months ago

      So this is related to the Entra ID / Azure option for BigQuery connector.


      Even if you don't select it when adding your source, it is overwritten with the preview feature "use new Google BigQuery connector implementation".