HHH-11083 : clarify that hibernate.cache.keys_factory is only supported when using Infinispan
This commit is contained in:
parent
6d8f93c103
commit
60d420b011
|
@ -70,8 +70,8 @@ Besides specific provider configuration, there are a number of configurations op
|
||||||
<entity type, tenant, identifier> to guarantee uniqueness in case that second-level cache stores all entities
|
<entity type, tenant, identifier> to guarantee uniqueness in case that second-level cache stores all entities
|
||||||
in single space. These tuples are then used as keys in the cache. When the second-level cache implementation
|
in single space. These tuples are then used as keys in the cache. When the second-level cache implementation
|
||||||
(incl. its configuration) guarantees that different entity types are stored separately and multi-tenancy is not
|
(incl. its configuration) guarantees that different entity types are stored separately and multi-tenancy is not
|
||||||
used, you can omit this wrapping to achieve better performance. This hint can be ignored by the second-level
|
used, you can omit this wrapping to achieve better performance. Currently, this property is only supported when
|
||||||
cache implementation, though. Valid values are:
|
Infinispan is configured as the second-level cache implementation. Valid values are:
|
||||||
* `default` (wraps identitifers in the tuple)
|
* `default` (wraps identitifers in the tuple)
|
||||||
* `simple` (uses identifiers as keys without any wrapping)
|
* `simple` (uses identifiers as keys without any wrapping)
|
||||||
* fully qualified class name that implements `org.hibernate.cache.spi.CacheKeysFactory`
|
* fully qualified class name that implements `org.hibernate.cache.spi.CacheKeysFactory`
|
||||||
|
|
Loading…
Reference in New Issue