Skip event reapply if all exclude options are set #6604
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
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.
What changed?
If all exclude types (enumspb.ResetReapplyExcludeType) are specified then we completely bypass event re-application.
(This is dependent on #6598)
Why?
It is sometimes necessary to prevent the workflow resetter from reading subsequent history events past the reset point (ex: data beyond reset point is corrupted). So in such cases the operator can specify all exclude types and the workflow resetter will not attempt to read data beyond reset point.
How did you test it?
Added new tests.
Potential risks
N/A
Documentation
N/A
Is hotfix candidate?
No