Add exception translation for DriverTimeoutException
#1399
Closed
Conversation
This file contains 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
spring-projects-issues
added
the
status: waiting-for-triage
mp911de
added
type: enhancement
|
It makes sense to add the mapping. Care to retain the original |
|
Of course, I will. So I'll just:
|
mipo256
force-pushed
the
feature/exception-translator-extend
branch
from
43563ef to
e211b95
Compare
|
@mp911de Done) |
mp911de
changed the title
DriverTimeoutException
mp911de
pushed a commit
that referenced
this pull request
Jul 3, 2023
mp911de
added a commit
that referenced
this pull request
Jul 3, 2023
Annotation serialVersionUID fields with Serial annotation. See #1399
|
Thank you for your contribution. That's merged and polished now. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Cassandra spring-data module does not recogize the
DriverTimeoutException, which essentially means that driver has timed out during interaction with cluster in general.Maybe we should consider to not throw
QueryTimeoutException, but create a separate one, specifically for this case.@mp911de @schauder please, take a look.