SAMZA-2336: Disable transactional state restore when not supported#1340
Merged
Conversation
…ommit are enabled
Contributor
Author
|
@mynameborat @prateekm can you take a look at this? |
mynameborat
approved these changes
Apr 8, 2020
This file contains hidden or 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
2 participants
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.
Feature: Disable transactional state for use cases that are not yet supported
Changes: Modifies the logic to accessing the
task.transactional.state.restore.enabledby returning false if standby or async commit are enabled.Tests: Added a unit test each for each permutation of configuration.
API Changes: None
Upgrade Instructions: None
Usage Instructions: None