feat(jdbc): implement OTel SDK and export tracing logic

[keshavdandeva]

b/491238299

This PR completes the implementation of the OpenTelemetry SDK lifecycle and cross-project authentication for the BigQuery JDBC driver. It introduces thread-safe caching of heavy OTel SDK instances to support multi-project tracing without global side effects.

Changes

BigQueryJdbcOpenTelemetry.java

• A ConcurrentHashMap caches OpenTelemetrySdk instances, keyed by a concatenated string of ProjectId and Credentials
• The getOpenTelemetry() method lazily loads and initializes the SDK only when requested and not present in the cache.
• A JVM shutdown hook closes each cached SDK to ensure pending traces are flushed on application exit.

BigQueryJdbcUrlUtility.java

• gcpTelemetryCredentials and gcpTelemetryProjectId are added to connection properties.

BigQueryJdbcOAuthUtility.java

• The isJson() helper method is changed from private to package-private to allow reuse in BigQueryJdbcOpenTelemetry.

BigQueryConnection.java

• Added new connection properties to be used
• Uses Boolean.TRUE.equals() when checking enableGcpLogExporter and enableGcpTraceExporter to safely handle cases where these properties are not specified null and avoid NullPointerException during auto-unboxing.

BigQueryJdbcOpenTelemetryTest.java

• New unit tests verify that SDK instances are correctly cached for identical keys and isolated for different keys.

BigQueryArrowStructTest.java

• A fix is applied to avoid varargs ambiguity in array creation, resolving a specific coercion failure in the structOfArrays test.

[gemini-code-assist]

Code Review

This pull request implements OpenTelemetry SDK initialization and OTLP exporting for the BigQuery JDBC driver. It introduces new connection properties for telemetry credentials and project IDs, and implements a caching mechanism for OTel SDK instances. Review feedback identifies a potential bug in the caching logic where configuration flags are missing from the cache key, and a resource leak caused by registering multiple shutdown hooks. Suggestions were provided to include flags in the cache key and use a single global shutdown hook to manage SDK lifecycle.

[keshavdandeva]

/gemini review

[gemini-code-assist]

Code Review

This pull request implements auto-configuration and caching for OpenTelemetry SDK instances within the BigQuery JDBC driver. It introduces new connection properties for GCP telemetry credentials and project IDs, enabling more flexible telemetry setup. The review feedback identifies critical risks regarding potential NullPointerExceptions when unboxing Boolean flags and suggests a more robust cache key construction to prevent key collisions in the SDK cache.

[keshavdandeva]

/gemini review

[gemini-code-assist]

Code Review

This pull request implements OpenTelemetry auto-configuration for the BigQuery JDBC driver, enabling the use of GCP-specific telemetry credentials and project IDs. It introduces a caching layer for OpenTelemetrySdk instances and a shutdown hook for resource cleanup. Feedback points out that the OTLP exporter configuration lacks proper authentication for GCP and identifies a potential memory leak in connection management. Further suggestions include refining the SDK caching logic to remove redundant keys and ensuring the shutdown hook is exception-safe.