Handle duplicate event inserts gracefully when using Postgresql #258
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.
Pull Request type
NOTE: Please remember to run
./gradlew spotlessApply
to fix any format violations.Changes in this PR
This PR changed the behavior of the PostgresExecutionDAO
insertEventExecution
method to handle the insertion of duplicate event entries gracefully. This allows the proper application flow to continue.Without this fix is not applied when exceptions will be thrown similar to this
The number of exceptions will grow as the source
queue_message
table is not cleared of the of the bad entries because of the exception thrown when they are processed.The new behavior matches that of the RedisExecutionDAO that skips adding events that have already been added.
Issue #