Skip to content

Conversation

@jayantsing-db
Copy link
Collaborator

@jayantsing-db jayantsing-db commented Jan 2, 2026

Description

NO_CHANGELOG=true

When LogLevel.OFF was set, setupLogger() returned early without configuring the JUL logger. This caused Java's default logging behavior to kick in, resulting in deprecation warnings (e.g., ignoreTransactions warnings) being logged to console despite logging being disabled.

Now properly initializes the logger with Level.OFF to suppress all output while using STDOUT to avoid file system access issues in restricted environments.

Fixes #1158

Testing

Manual testing

Additional Notes to the Reviewer

When LogLevel.OFF was set, setupLogger() returned early without configuring the JUL logger. This caused Java's default logging behavior to kick in, resulting in deprecation warnings (e.g., ignoreTransactions warnings) being logged to console despite logging being disabled.

Now properly initializes the logger with Level.OFF to suppress all output while using STDOUT to avoid file system access issues in restricted environments.

Fixes databricks#1158
@jayantsing-db jayantsing-db enabled auto-merge (squash) January 2, 2026 10:53
@jayantsing-db jayantsing-db merged commit 6e84664 into databricks:main Jan 2, 2026
12 of 14 checks passed
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.

[BUG] Inconsistent behavior of connection.IgnoreTransactions and AUTOCOMMIT handling

2 participants