Add deprecation for Java-based event ruler #11964
Merged
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
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 4m 2s ⏱️ Results for commit 24b6a85. |
dominikschubert
approved these changes
Nov 29, 2024
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.
Depends on #11960
Motivation
The Java-based event ruler is deprecated because our latest Python-native implementation introduced in 4.0.3 is faster, achieves great AWS parity, and fixes compatibility issues with the StepFunctions JSONata feature.
Changes
EVENT_RULE_ENGINEconfig used for opt-into the Java-based event rulerPOLL_INTERVAL_SECNotes
We now have a comprehensive test suite and can be confident that (almost) all cases are covered.