#1036: Use Event timestamp instead of Changlog Date to decide if the event should be applied #1037
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
Contributor
MichaelVonB
commented
Aug 19, 2024
MichaelVonB
commented
- Introduced new column to store event timestamp as version Info
- Introduced configuration property to allow JPA-View to process old events even when more recent ones were already applied
- closes Use technical event date for optimistic locking #1036
…ator for event order - closes #1036
MichaelVonB
added
Type: enhancement
S-Tim
reviewed
Aug 20, 2024
view/jpa/src/test/kotlin/io/holunda/polyflow/view/jpa/JpaPolyflowViewServiceDataEntryITest.kt
Show resolved
Hide resolved
S-Tim
approved these changes
Aug 20, 2024
zambrovski
deleted the
1036-use-technical-event-date-for-optimistic-locking
branch
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.