-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change way of working on DlqDeserializationExceptionHandler. #75
Merged
loicgreffier
merged 4 commits into
main
from
feat/add_retries_for_DlqDeserializationExceptionHandler.java
Sep 6, 2023
Merged
Change way of working on DlqDeserializationExceptionHandler. #75
loicgreffier
merged 4 commits into
main
from
feat/add_retries_for_DlqDeserializationExceptionHandler.java
Sep 6, 2023
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
clvacher
requested changes
Aug 24, 2023
return DeserializationHandlerResponse.CONTINUE; | ||
// here we only have exception like UnknownHostException for example or TimeoutException ... | ||
// example: we cannot ask schema registry De | ||
return DeserializationHandlerResponse.FAIL; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Coudl the whole method be optimized for readability, i.e with a finally statement?
@@ -52,7 +59,9 @@ public DeserializationHandlerResponse handle(ProcessorContext processorContext, | |||
return DeserializationHandlerResponse.FAIL; | |||
} | |||
|
|||
return DeserializationHandlerResponse.CONTINUE; | |||
// here we only have exception like UnknownHostException for example or TimeoutException ... | |||
// example: we cannot ask schema registry De |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfinished comment
…on pill ☠ and CONTINUE and FAIL only if we had network issue (schema registry timeout for example) 💻
clvacher
force-pushed
the
feat/add_retries_for_DlqDeserializationExceptionHandler.java
branch
from
September 6, 2023 15:53
d19248c
to
a4aefde
Compare
Kudos, SonarCloud Quality Gate passed! |
clvacher
approved these changes
Sep 6, 2023
loicgreffier
changed the title
change way of working on DlqDeserializationExceptionHandler.
Change way of working on DlqDeserializationExceptionHandler.
Sep 6, 2023
loicgreffier
deleted the
feat/add_retries_for_DlqDeserializationExceptionHandler.java
branch
September 6, 2023 16:04
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
Change DlqDeserializationExceptionHandler.
1- catch poison pill ☠ - sent a message in DLQ and CONTINUE (if we had trouble to produce in dlq : FAIL)
2- FAIL only if we have a network issue (schema registry timeout for example)