@RedisHash("persons")
public class Person {@Id String id;String firstname;String lastname;Address address;
}

public interface PersonRepository extends CrudRepository<Person, String> {}

@Configuration
@EnableRedisRepositories
public class ApplicationConfig {@Beanpublic RedisConnectionFactory connectionFactory() {return new JedisConnectionFactory();}@Beanpublic RedisTemplate<?, ?> redisTemplate() {RedisTemplate<byte[], byte[]> template = new RedisTemplate<byte[], byte[]>();return template;}
}

_class = org.example.Person
id = e2c7dcee-b8cd-4424-883e-736ce564363e
firstname = rand
lastname = al’thor
address.city = emond's field
address.country = andor

@WritingConverter
public class AddressToBytesConverter implements Converter<Address, byte[]> {private final Jackson2JsonRedisSerializer<Address> serializer;public AddressToBytesConverter() {serializer = new Jackson2JsonRedisSerializer<Address>(Address.class);serializer.setObjectMapper(new ObjectMapper());}@Overridepublic byte[] convert(Address value) {return serializer.serialize(value);}
}@ReadingConverter
public class BytesToAddressConverter implements Converter<byte[], Address> {private final Jackson2JsonRedisSerializer<Address> serializer;public BytesToAddressConverter() {serializer = new Jackson2JsonRedisSerializer<Address>(Address.class);serializer.setObjectMapper(new ObjectMapper());}@Overridepublic Address convert(byte[] value) {return serializer.deserialize(value);}
}

@WritingConverter
public class AddressToMapConverter implements Converter<Address, Map<String,byte[]>> {@Overridepublic Map<String,byte[]> convert(Address source) {return singletonMap("ciudad", source.getCity().getBytes());}
}@ReadingConverter
public class MapToAddressConverter implements Converter<Address, Map<String, byte[]>> {@Overridepublic Address convert(Map<String,byte[]> source) {return new Address(new String(source.get("ciudad")));}
}

@Configuration
@EnableRedisRepositories(keyspaceConfiguration = MyKeyspaceConfiguration.class)
public class ApplicationConfig {//... RedisConnectionFactory and RedisTemplate Bean definitions omittedpublic static class MyKeyspaceConfiguration extends KeyspaceConfiguration {@Overrideprotected Iterable<KeyspaceSettings> initialConfiguration() {return Collections.singleton(new KeyspaceSettings(Person.class, "persons"));}}
}

@Configuration
@EnableRedisRepositories
public class ApplicationConfig {//... RedisConnectionFactory and RedisTemplate Bean definitions omitted@Beanpublic RedisMappingContext keyValueMappingContext() {return new RedisMappingContext(new MappingConfiguration(new MyKeyspaceConfiguration(), new IndexConfiguration()));}public static class MyKeyspaceConfiguration extends KeyspaceConfiguration {@Overrideprotected Iterable<KeyspaceSettings> initialConfiguration() {return Collections.singleton(new KeyspaceSettings(Person.class, "persons"));}}
}

给定示例Person实体，我们可以通过注释属性为firstname创建一个索引@Indexed。

索引是为实际属性值构建的。挽救两个人，例如。“rand”和“aviendha”导致设置如下所示的索引。

SADD persons:firstname:rand e2c7dcee-b8cd-4424-883e-736ce564363e
SADD persons:firstname:aviendha a9d4b3a0-50d3-4538-a2fc-f7fc2581ee56

在嵌套元素上也可以有索引。假设Address有一个城市属性，注明@Indexed。在这种情况下，一旦person.address.city不是null，我们就为每个城市设置了套数。

SADD persons:address.city:tear e2c7dcee-b8cd-4424-883e-736ce564363e

此外，编程设置允许在地图键和列表属性上定义索引。

与密钥空间相同，可以配置索引而不需要注释实际的域类型。

假设该Address类型包含保存特定地址的地理坐标的location类型属性Point。通过@GeoIndexed使用Redis GEO命令添加这些值来注释属性。

在上面的例子中，GEOADD使用对象id作为成员的名字来存储lon / lat值。查找器方法允许查询这些值的用法Circle或Point, Distance组合。

public class TimeToLiveOnProperty {@Idprivate String id;@TimeToLiveprivate Long expiration;
}public class TimeToLiveOnMethod {@Idprivate String id;@TimeToLivepublic long getTimeToLive() {return new Random().nextLong();}
}

public interface PersonRepository extends CrudRepository<Person, String> {List<Person> findByFirstname(String firstname);
}

String user = //...List<RedisSession> sessionsByUser = template.find(new RedisCallback<Set<byte[]>>() {public Set<byte[]> doInRedis(RedisConnection connection) throws DataAccessException {return connection.sMembers("sessions:securityContext.authentication.principal.username:" + user);}}, RedisSession.class);

当所有涉及的密钥映射到相同的插槽时，一些命令只能在服务器端处理SINTER并且SUNION只能处理。否则，计算必须在客户端完成。因此将密钥空间固定到单个插槽可以立即使用Redis服务器计算。