Use non-deprecated user_agent_entry param in DatabricksSqlHook - #72103
Open
peloyeje wants to merge 1 commit into
Open
Use non-deprecated user_agent_entry param in DatabricksSqlHook#72103peloyeje wants to merge 1 commit into
peloyeje wants to merge 1 commit into
Conversation
peloyeje
force-pushed
the
fix/databricks-sql-hook-user-agent-entry
branch
from
August 26, 2026 14:20
e81f760 to
f9f08e0
Compare
potiuk
approved these changes
Aug 26, 2026
databricks-sql-connector renamed _user_agent_entry to user_agent_entry and only keeps the old name for backward compatibility, logging a deprecation warning on every connection opened through DatabricksSqlHook.get_conn(). Pass the current parameter name instead.
potiuk
force-pushed
the
fix/databricks-sql-hook-user-agent-entry
branch
from
August 27, 2026 10:23
f9f08e0 to
c569929
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes: #72102
databricks-sql-connector'sSessionrenamed_user_agent_entrytouser_agent_entryand only keeps the old name for backward compatibility,logging a deprecation warning on every connection opened through
DatabricksSqlHook.get_conn(). This switches the hook to the currentparameter name.
No behavior change:
user_agent_entryis supported by everydatabricks-sql-connector version this provider currently allows
(>=4.4.0).
Was generative AI tooling used to co-author this PR?