Curious question
Why in the series of OpsFor* methods of RedisTemplate, opsForHash() always returns a new instance object, valueOps, listOps, setOps, zSetOps and other data structures return final modified instantiated property objects. Is there a particular reason for this
dependency
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-data-redis</artifactId>
<version>3.2.2</version>
</dependency>opsForHash() Method
this is opsForHash() method body for 3.2.2 version
public <HK, HV> HashOperations<K, HK, HV> opsForHash() {
return new DefaultHashOperations(this);
}and the next code is some opsFor* that return the singleton object
private final ValueOperations<K, V> valueOps = new DefaultValueOperations(this);
private final ListOperations<K, V> listOps = new DefaultListOperations(this);
private final SetOperations<K, V> setOps = new DefaultSetOperations(this);
private final StreamOperations<K, ?, ?> streamOps = new DefaultStreamOperations(this, ObjectHashMapper.getSharedInstance());
private final ZSetOperations<K, V> zSetOps = new DefaultZSetOperations(this);
private final GeoOperations<K, V> geoOps = new DefaultGeoOperations(this);
private final HyperLogLogOperations<K, V> hllOps = new DefaultHyperLogLogOperations(this);
private final ClusterOperations<K, V> clusterOps = new DefaultClusterOperations(this);I would like to know why the design is like this, I searched for related questions but found no discussion about it
Curious question
Why in the series of
OpsFor*methods ofRedisTemplate,opsForHash()always returns a new instance object,valueOps,listOps,setOps,zSetOpsand other data structures return final modified instantiated property objects. Is there a particular reason for thisdependency
opsForHash() Method
this is opsForHash() method body for
3.2.2versionand the next code is some opsFor* that return the singleton object
I would like to know why the design is like this, I searched for related questions but found no discussion about it