Re: [I] Attempting to drop a Bigquery table through cur.execute throws Error about "storage read API" [arrow-adbc]

["dataders (via GitHub)" <gi...@apache.org>]

dataders commented on issue #2173:
URL: https://github.com/apache/arrow-adbc/issues/2173#issuecomment-3136584210

   Hi friends -- I've just reopened https://github.com/dbt-labs/dbt-fusion/issues/236 there's more context in https://github.com/dbt-labs/dbt-fusion/issues/236#issuecomment-3136522903.
   
   but we've got two separate reports of this.
   
   TL;DR My hunch is that it's discrepancy in required permissions when connecting with ADBC & Go SDK compared to both the BQ CLI as well as the Python driver (invoked via dbt Core).
   
   This might be a red herring, but bc the way the dbt Fusion works, we always see this failure when attempting to query the information schema of a project.
   
   `{BQ_project}.public.INFORMATION_SCHEMA.COLUMNS`
   
   a very silly theory is that perhaps the Go SDK doesn't correctly pass the FQN when identifiers are escaped with backticks (`` ` ``)? A related example is the BQ CLI only accepts `` ` `` with the `--legacy-sql=false` flag.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org