From d7ba2a6ac2b3924c3d4ad76ba6d445f98688286e Mon Sep 17 00:00:00 2001 From: Christoph Strobl Date: Fri, 20 Jan 2017 14:53:07 +0100 Subject: [PATCH] =?UTF-8?q?DATAREDIS-594=20-=20Update=20"what=E2=80=99s=20?= =?UTF-8?q?new"=20section=20in=20reference=20documentation.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- src/main/asciidoc/new-features.adoc | 7 ++++++- src/main/asciidoc/reference/redis.adoc | 1 + 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/src/main/asciidoc/new-features.adoc b/src/main/asciidoc/new-features.adoc index 5e02b6bb7..80ccf0be6 100644 --- a/src/main/asciidoc/new-features.adoc +++ b/src/main/asciidoc/new-features.adoc @@ -14,9 +14,14 @@ New and noteworthy in the latest releases. [[new-in-1.8.0]] == New in Spring Data Redis 1.8 +* Upgrade to Jedis 2.9. +* Upgrade to `Lettuce` 4.2 (Note: Lettuce 4.2 requires Java 8). * Support for Redis http://redis.io/commands#geo[GEO] commands. * Support for Geospatial Indexes using Spring Data Repository abstractions (see <>). -* Upgrade to `Lettuce` 4.2. Lettuce 4.2 requires Java 8. +* `MappingRedisConverter` based `HashMapper` implementation (see <>). +* Support for `PartialUpdate` in repository support (see <>). +* SSL support for connections to Redis cluster. +* Support for `client name` via `ConnectionFactory` when using Jedis. [[new-in-1.7.0]] == New in Spring Data Redis 1.7 diff --git a/src/main/asciidoc/reference/redis.adoc b/src/main/asciidoc/reference/redis.adoc index d68ee1218..154084ebf 100644 --- a/src/main/asciidoc/reference/redis.adoc +++ b/src/main/asciidoc/reference/redis.adoc @@ -290,6 +290,7 @@ public void useCallback() { From the framework perspective, the data stored in Redis is just bytes. While Redis itself supports various types, for the most part these refer to the way the data is stored rather than what it represents. It is up to the user to decide whether the information gets translated into Strings or any other objects. The conversion between the user (custom) types and raw data (and vice-versa) is handled in Spring Data Redis through the `RedisSerializer` interface (package `org.springframework.data.redis.serializer`) which as the name implies, takes care of the serialization process. Multiple implementations are available out of the box, two of which have been already mentioned before in this documentation: the `StringRedisSerializer` and the `JdkSerializationRedisSerializer`. However one can use `OxmSerializer` for Object/XML mapping through Spring 3 http://docs.spring.io/spring/docs/current/spring-framework-reference/html/oxm.html[OXM] support or either `JacksonJsonRedisSerializer`, `Jackson2JsonRedisSerializer` or `GenericJackson2JsonRedisSerializer` for storing data in http://en.wikipedia.org/wiki/JSON[JSON] format. Do note that the storage format is not limited only to values - it can be used for keys, values or hashes without any restrictions.[[redis:serializer]] +[[redis.hashmappers.root]] == Hash mapping Data can be stored using various data structures within Redis. You already learned about `Jackson2JsonRedisSerializer` which can convert objects