fix(bigquery-jdbc): pass connection proxy settings to OpenTelemetry exporters

[keshavdandeva]

b/543818095

Changes

1. Driver Implementation (BigQueryJdbcOpenTelemetry.java & BigQueryConnection.java):

   • Trace Exporter Proxy Support: Passed proxyProperties to getOpenTelemetry(...), configuring ProxyOptions (via custom ProxySelector) on OtlpHttpSpanExporterBuilder.
   • Cache Key Isolation: Added proxyHost and proxyPort to SdkCacheKey so different proxy configurations receive dedicated OpenTelemetry SDK instances.
   • Telemetry Metadata: Passed this.headerProvider to createLoggingClient(...) for telemetry attribution.

2. Integration Tests (ITOpenTelemetryTest.java):

   • Added testExecute_withHttpProtocol_andDirectTraceVerification() to verify OpenTelemetry HTTP trace delivery end-to-end through proxies directly via Cloud Trace API (independent of Cloud Logging).
   • Refactored verifyAndFetchTrace(...) to automatically route TraceServiceClient requests through proxy tunnels when ProxyHost/ProxyPort are present on the connection URL.

3. Unit Tests:

   • Updated BigQueryConnectionTest.java and BigQueryJdbcOpenTelemetryTest.java to match new method signatures.

[gemini-code-assist]

Code Review

This pull request introduces proxy support for OpenTelemetry HTTP span exporters and configures transport options and header providers for the GCP Logging client. Specifically, it parses proxy properties from the connection settings and applies them when building the OtlpHttpSpanExporter. The review feedback suggests adding validation and error handling when parsing the proxy port to prevent potential NumberFormatException or out-of-bounds port values from causing abrupt connection failures.

[keshavdandeva]

/gemini review

[gemini-code-assist]

Code Review

This pull request adds proxy support for OpenTelemetry HTTP span exporters in the BigQuery JDBC driver by parsing, caching, and applying proxy configurations during SDK initialization. It also updates the logging client to support a HeaderProvider. The feedback suggests improving the robustness of the proxy configuration parsing by adding null/empty checks, handling potential number format exceptions, and using unresolved socket addresses to avoid blocking DNS resolution.