This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
Added dedicated methods to serialize/deserialize input/output data #2919
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.
Pull Request type
./gradlew generateLock saveLock
to refresh dependencies)Changes in this PR
Introduced methods for reading input and output data during the serialization process. The existing getters have logic to check to where the payload exists and return them. During serialization, the getter returns the large payload which is then persisted along with the execution data.
Issue #2899
Alternatives considered
This is a temporary patch to fix the issue introduced in 3.6.0 and 3.6.1. A more elaborate fix is to refactor all references of
getInput
orgetOutput
methods to use a new method and remove the additional logic (of checking the external storage path) from them.