feat(PECOBLR-2328): bump databricks-sql-connector upper bound to <4.1.6#1363
Merged
feat(PECOBLR-2328): bump databricks-sql-connector upper bound to <4.1.6#1363
Conversation
Bump databricks-sql-connector to >=4.1.5 and expose the new _retry_server_directed_only parameter (default: false) to prevent duplicate writes caused by blind 503 retries on ExecuteStatement. Users can opt in via connection_parameters in profiles.yml. PECOBLR-2328 Co-authored-by: Isaac
Co-authored-by: Isaac
tejassp-db
changed the title
tejassp-db
commented
Mar 24, 2026
Coverage report
This PR does not seem to contain any modification to coverable code. |
sd-db
changed the title
_retry_server_directed_only connection parameter
sd-db
reviewed
Apr 15, 2026
Collaborator
sd-db
left a comment
sd-db
left a comment
There was a problem hiding this comment.
Let us also update the CHANGELOG.md to list that we are updating the python-sql-connector dependency
…eader The connector already defaults this parameter to False, so the setdefault in credentials.py was redundant. Users opt in via connection_parameters directly. Also fix the parameter name (was renamed during connector PR review) and tighten upper bound to <4.1.6. Co-authored-by: Isaac
sd-db
reviewed
Apr 16, 2026
sd-db
changed the title
_retry_server_directed_only connection parameter
sd-db
changed the title
sd-db
changed the title
The TestDatabricksCredentialsPreDeserialize tests covered pre-existing setdefaults (_retry_stop_after_attempts_count, _retry_delay_max) that this PR does not modify, making them out of scope. Co-authored-by: Isaac
…directed-only # Conflicts: # CHANGELOG.md
sd-db
previously approved these changes
Apr 16, 2026
Co-authored-by: Isaac
sd-db
approved these changes
Apr 16, 2026
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.
Summary
databricks-sql-connectorupper bound from<4.1.4to<4.1.6, allowing users to install connector4.1.54.1.5introduced_respect_server_retry_after_header, which users can now opt into viaconnection_parametersinprofiles.ymlContext
Customers using
use_materialization_v2: trueexperience duplicate rows when the server returns HTTP 503 after already committing an INSERT. The connector blindly retries, causing data to be written twice. With_respect_server_retry_after_header: true, retries only occur when the server explicitly sends aRetry-Afterheader, preventing duplicate writes from infrastructure-level 503s.Test plan
hatch run unit)dbt debug+dbt runsucceed with default profile (connector defaultFalseapplied)dbt debug+dbt runsucceed with_respect_server_retry_after_header: trueexplicitly set