fix(bigquery-jdbc): fix manual commit mode failure for non-US regions

[yagudin10]

Problem

Manual commit mode fails when using BigQuery JDBC with non-US datasets.

STR (Steps to Reproduce)

1. Create BigQuery JDBC connection
2. Set a non-US location (e.g. EU) via Location property
3. Enable session mode (EnableSession = 1)
4. Disable auto-commit:

   conn.setAutoCommit(false);

5. Execute a simple query:

SELECT 1;

ER (Expected Result)

• Query executes successfully in manual commit mode
• BigQuery uses configured Location (e.g. EU)
• No region mismatch errors occur

AR (Actual Result)

Query execution fails with:

GoogleJsonResponseException: 400 Bad Request
INVALID_ARGUMENT
Error: 3848323

Sample java code:

String jdbcUrl = "jdbc:bigquery://https://www.googleapis.com/bigquery/v2:443";

Properties props = new Properties();
props.put("OAuthType", "0");
props.put("OAuthPvtKeyPath", "<key-file-path>");
props.put("ProjectId", "<project-id>");
props.put("Location", "EU");
props.put("EnableSession", "1");

try (Connection conn = DriverManager.getConnection(jdbcUrl, props)) {
    conn.setAutoCommit(false);

    try (PreparedStatement ps = conn.prepareStatement("SELECT 1;")) {
        ps.execute();
    }
}

[gemini-code-assist]

Code Review

This pull request updates BigQueryImpl.java to explicitly set the location for a new job using the configured options when generating a default JobId. This prevents jobs from being created with an incorrect location, such as when running in transaction mode outside the US. Additionally, telemetry tests in HttpBigQueryRpcTest.java have been updated to reflect the inclusion of the location in the job ID. No review comments were provided.

[logachev]

/gcbrun

[logachev]

Thank you for finding & fixing this!

[logachev]

/gcbrun