#104561: Added variable 'replication:classic' #1003
Conversation
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
This boolean can be used to choose the replication execution framework mode. Either use 'true' to use historic pipeline-based approach, or 'false' in order to use the new implementation.
Test Results0 tests 0 ✅ 0s ⏱️ Results for commit bad54dc. |
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.
This boolean can be used to choose the replication execution framework mode. Either use 'true' to use historic pipeline-based approach, or 'false' in order to use the new implementation.
PR Type
Release
Be sure that pull requests are build according to the defined release process here. As a main part to mention here is that the semantic version type will be read from the commit messages (
BREAKING CHANGE(icm):marks a major change,feat(icm):marks minor changes and the rest will be patch. So the developer must already know and is responsible.What Is the Current Behavior?
Currently the ICM replication processes use the historic pipeline based execution framework.
Issue Number: Closes #
What Is the New Behavior?
Using the newly provided value 'replication:classic:[true|false]', this can be switched to the new fully Java based framwork. Use classic:false to do so.
Does this PR Introduce a Breaking Change?
Other Information