StepFunctions: Fix Evaluation of Nested Map Runs #12033
Merged
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.
Motivation
Currently, the SFN v2 is unable to evaluate nested MapRun states, resulting in pickling runtime errors #9809. This was due to an unecessary deep copy of the map run program, which contains unserialisable objects such as locks. The deep copy is not considered necessary as EvalComponents are stateless by design, and can therefore be shared by multiple runtimes. These changes address such issue and add a relevant snapshot test.
Changes