Spring Data for VMware GemFire
Interface ExpiringRegionFactoryBean<K,V>
- All Known Implementing Classes:
CacheTypeAwareRegionFactoryBean,ClientRegionFactoryBean,GenericRegionFactoryBean,LocalRegionFactoryBean,PartitionedRegionFactoryBean,PeerRegionFactoryBean,ReplicatedRegionFactoryBean
public interface ExpiringRegionFactoryBean<K,V>
The
ExpiringRegionFactoryBean interface signifies Region FactoryBeans
that support Expiration configuration. That is, Region's capable of expiring both entries
as well as the Region itself.
Expiration policies may either be expressed as ExpirationAttributes or using a CustomExpiry
object enable the application developer to specify custom expiration criteria.
Apache Geode and Pivotal GemFire supports both Idle Timeout (TTI) as well as Time-to-Live (TTL) expiration policies
at both the Region level as well as for entries.- Since:
- 2.1.0
- See Also:
-
CustomExpiryExpirationAttributesRegion
-
Method Summary
Modifier and TypeMethodDescriptionvoidsetCustomEntryIdleTimeout(org.apache.geode.cache.CustomExpiry<K, V> customEntryIdleTimeout) voidsetCustomEntryTimeToLive(org.apache.geode.cache.CustomExpiry<K, V> customEntryTimeToLive) voidsetEntryIdleTimeout(org.apache.geode.cache.ExpirationAttributes entryIdleTimeout) voidsetEntryTimeToLive(org.apache.geode.cache.ExpirationAttributes entryTimeToLive) voidsetRegionIdleTimeout(org.apache.geode.cache.ExpirationAttributes regionIdleTimeout) voidsetRegionTimeToLive(org.apache.geode.cache.ExpirationAttributes regionTimeToLive)
-
Method Details
-
setCustomEntryIdleTimeout
-
setCustomEntryTimeToLive
-
setEntryIdleTimeout
void setEntryIdleTimeout(org.apache.geode.cache.ExpirationAttributes entryIdleTimeout) -
setEntryTimeToLive
void setEntryTimeToLive(org.apache.geode.cache.ExpirationAttributes entryTimeToLive) -
setRegionIdleTimeout
void setRegionIdleTimeout(org.apache.geode.cache.ExpirationAttributes regionIdleTimeout) -
setRegionTimeToLive
void setRegionTimeToLive(org.apache.geode.cache.ExpirationAttributes regionTimeToLive)
-