Skip to content

Conversation

@davidhcoe
Copy link
Contributor

In the current iteration, no DefaultLocation is specified for the internal BigQueryClient. Since this is not specified, the BigQuery API makes this default to "US" which is causing failures for some users. This PR adds a new parameter to set the DefaultLocation for the BigQueryClient, which then uses that same value for creating datasets and other location-based activitities.

@github-actions github-actions bot added this to the ADBC Libraries 21 milestone Sep 29, 2025
Copy link
Contributor

@CurtHagenlocher CurtHagenlocher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

While I think this change is good, is it our expectation that the user will have to enter an additional parameter when connecting to BigQuery using this driver? Is this something whose default value can be derived from the project or the user account in some fashion so that the user doesn't need to enter it? How does the Go BigQuery driver do this?

@CurtHagenlocher CurtHagenlocher merged commit 51e854b into apache:main Sep 29, 2025
6 checks passed
@davidhcoe
Copy link
Contributor Author

If the user doesn't specify (which we don't today), then the API defaults to US. I will see whether the Go driver deals with this at all.

@davidhcoe
Copy link
Contributor Author

It basically does the same thing:

if c.location != "" {
.

I tried to determine location based on the project ID, but that is not something that is supported.

@CurtHagenlocher
Copy link
Contributor

Do we have any way to figure out what the ODBC driver is doing?

@davidhcoe davidhcoe deleted the dev/bq-specify-location branch October 24, 2025 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants