DATAREDIS-390 - Improve Support for JSON Serialization. #136
Conversation
This file contains 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
Prepare issue branch.
thomasdarimont
force-pushed
the
issue/DATAREDIS-390
branch
from
6dfb564
to
d3c8821
Compare
thomasdarimont
pushed a commit
that referenced
this pull request
Apr 7, 2015
Introduced GenericJackson2RedisSerializer that is capable of serialising arbitrary java objects into redis without a priority knowledge of the used types. This is achieved by encoding the actual type information with the value. Previously users had to use Jackson2RedisSerializer which only supported serialising one type. Original pull request: #136.
thomasdarimont
force-pushed
the
issue/DATAREDIS-390
branch
from
d3c8821
to
6f6c65e
Compare
thomasdarimont
pushed a commit
that referenced
this pull request
Apr 7, 2015
Introduced GenericJackson2RedisSerializer that is capable of serialising arbitrary java objects into redis without a priority knowledge of the used types. This is achieved by encoding the actual type information with the value. Previously users had to use Jackson2RedisSerializer which only supported serialising one type. Original pull request: #136.
thomasdarimont
force-pushed
the
issue/DATAREDIS-390
branch
from
6f6c65e
to
afd4016
Compare
thomasdarimont
pushed a commit
that referenced
this pull request
Apr 7, 2015
Introduced GenericJackson2RedisSerializer that is capable of serialising arbitrary java objects into redis without a priority knowledge of the used types. This is achieved by encoding the actual type information with the value. Previously users had to use Jackson2RedisSerializer which only supported serialising one type. Original pull request: #136.
Introduced GenericJackson2RedisSerializer that is capable of serialising arbitrary java objects into redis without a priority knowledge of the used types. This is achieved by encoding the actual type information with the value. Previously users had to use Jackson2RedisSerializer which only supported serialising one type. Original pull request: #136.
thomasdarimont
force-pushed
the
issue/DATAREDIS-390
branch
from
afd4016
to
9879afa
Compare
We now support optional type aliases to be defined via the constructor of GenericJackson2JsonRedisSerializer.
|
fixed in #145 |
|
We do need this!But it's likely not accepted, pity~ |
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.
Introduced GenericJackson2RedisSerializer that is capable of serialising arbitrary java objects into redis without a priority knowledge of the used types. This is achieved by encoding the actual type information with the value. Previously users had to use Jackson2RedisSerializer which only supported serialising one type.