ci(bigquery): configure us-east7 endpoint overrides in Kokoro integration tests - #13971
ci(bigquery): configure us-east7 endpoint overrides in Kokoro integration tests#13971jinseopkim0 wants to merge 1 commit into
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds region-specific environment variables for BigQuery and BigQuery Storage endpoints (BIGQUERY_ENDPOINT and BIGQUERY_STORAGE_ENDPOINT) to the Kokoro presubmit and integration configuration files. There are no review comments, and I have no feedback to provide.
7c5dbbd to
52eb330
Compare
52eb330 to
81baaa3
Compare
|
|
||
| @Test | ||
| void testListDatasets() { | ||
| // This test queries public datasets, which are not supported by regional endpoints. |
There was a problem hiding this comment.
IIUC, these tests won't run at all in the CIs? I don't think there is a way to dynamically switch between the two or have two jobs.
For the tests that touch the public dataset, would it be better to have two BQ clients?
e.g.
us-east-7 for stuff that creates new datasets/ table
normal endpoint to stuff that touches public datasets?
Maybe a long term fix to align everything would be to rewrite the public dataset tests to create local datasets so we don't need a split of endpoints?
2 participants
Configures the
BIGQUERY_ENDPOINTandBIGQUERY_STORAGE_ENDPOINTenvironment variables in the Kokoro presubmit and GraalVM test configuration files to point to theus-east7regional endpoints. This allows integration tests to execute against the Wave 0 canary region in CI.CI Testing Configuration Matrix
us-east7): Configured in presubmit configs (like bigquery-integration.cfg and bigquerystorage-integration.cfg). Skips integration tests that query public datasets (which are not supported on regional endpoints).b/472499857