Note: This issue was originally created as apache/arrow-adbc#3282 by serramatutu and was later copied here as part of migrating active development of the BigQuery Go driver to adbc-drivers/bigquery.
What feature or improvement would you like to see?
Per this thread, BigQuery's API returns an error whenever the credential lacks roles/bigquery.readSessionUser.
I suggest we either:
- Try using the Read API and fall back to the regular REST API in case the user has
roles/bigquery.jobUser but not roles/bigquery.readSessionUser
- Add a driver parameter like
adbc.bigquery.backend_api which defaults to read_api but can also be set to jobs_api to allow users to set which API they want to use.
Note: This issue was originally created as apache/arrow-adbc#3282 by serramatutu and was later copied here as part of migrating active development of the BigQuery Go driver to adbc-drivers/bigquery.
What feature or improvement would you like to see?
Per this thread, BigQuery's API returns an error whenever the credential lacks
roles/bigquery.readSessionUser.I suggest we either:
roles/bigquery.jobUserbut notroles/bigquery.readSessionUseradbc.bigquery.backend_apiwhich defaults toread_apibut can also be set tojobs_apito allow users to set which API they want to use.