Skip to content

fix(bigquery-jdbc): fix missing logger instances - #14733

Merged
logachev merged 1 commit into
mainfrom
kirl/logger_leak
Oct 22, 2026
Merged

logachev merged 1 commit into
mainfrom
kirl/logger_leak

Conversation

@logachev

Copy link
Copy Markdown
Contributor

More instances of per-class logger instances, follow up for #14716

@logachev
logachev requested review from a team as code owners October 22, 2026 17:27

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request refactors logger instantiation across several classes, including BigQueryJdbcBulkInsertWriter, BigQueryParameterHandler, BigQueryPreparedStatement, and BigQueryResultSetMetadata, by changing the LOG field from an instance variable to a static final variable. This change prevents the redundant registration of child loggers on the driver root logger for every new object instance. Additionally, unit tests have been added to BigQueryJdbcCustomLoggerTest to verify that creating multiple instances of these classes does not leak or register additional child loggers. There are no review comments, and I have no further feedback to provide.

@logachev
logachev merged commit 0e822dc into main Oct 22, 2026
197 checks passed
@logachev
logachev deleted the kirl/logger_leak branch October 22, 2026 18:11
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