Conversation
cathleeny
requested review from
eric-wang-1990,
vikrantpuppala and
vuanhphung
September 23, 2026 01:07
Collaborator
|
Can you add some context on why this change is needed? |
Signed-off-by: Cathleen Yan <58714163+cathleeny@users.noreply.github.com>
cathleeny
force-pushed
the
fix/query-timeout-sqlstate
branch
from
September 23, 2026 18:41
ab03afa to
ce39904
Compare
Collaborator
Author
|
Closing since this is not needed |
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.
Description
Return SQLSTATE
HYT00when the client-side query timeout expires, matching the Databricks reference JDBC driver.The SQLSTATE is set only at the client deadline enforcement points: the shared polling timeout handler used by SEA and Thrift, and the outer statement timeout. The default
DatabricksTimeoutExceptionmapping is left unchanged so this fix does not globally relabel server-originated or other timeout errors.Testing
jdbc-coreunit suite before the scoping refinement: 3,571 passed, 0 failed