Fix ms.hgetall return value interpretation #196
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.
Description
(this PR should not appear in the changelog: it affects only the changes on the MemoryStorage controller in the
4.x
SDK version)The
hgetall
result was interpreted as an array of, alternatively, key and its associated value, and a mapper function was plugged into this method to ensure a proper JSON object was returned to the client.But the result of this redis call is already a POJO, so the mapping is unnecessary and causes a SDK crash.