Interface StoreConfiguration

All Known Implementing Classes:
AbstractJdbcStoreConfiguration, AbstractSchemaJdbcConfiguration, AbstractSegmentedStoreConfiguration, AbstractStoreConfiguration, ClusterLoaderConfiguration, CustomStoreConfiguration, JdbcStringBasedStoreConfiguration, QueriesJdbcStoreConfiguration, RemoteStoreConfiguration, RocksDBStoreConfiguration, SFSToSIFSConfiguration, SingleFileStoreConfiguration, SoftIndexFileStoreConfiguration, TableJdbcStoreConfiguration

public interface StoreConfiguration
StoreConfiguration contains generic configuration elements available to all the stores.
Since:
5.2
Author:
Tristan Tarrant, Mircea Markus
  • Method Details

    • async

      Configuration for the async cache loader. If enabled, this provides you with asynchronous writes to the cache store, giving you 'write-behind' caching.
    • purgeOnStartup

      boolean purgeOnStartup()
      If true, purges this cache store when it starts up.
    • fetchPersistentState

      boolean fetchPersistentState()
      If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled. Persistent state transfer with a shared cache store does not make sense, as the same persistent store that provides the data will just end up receiving it. Therefore, if a shared cache store is used, the cache will not allow a persistent state transfer even if a cache store has this property set to true. Finally, setting it to true only makes sense if in a clustered environment, and only 'replication' and 'invalidation' cluster modes are supported.
    • ignoreModifications

      boolean ignoreModifications()
      If true, any operation that modifies the cache (put, remove, clear, store...etc) won't be applied to the cache store. This means that the cache store could become out of sync with the cache.
    • writeOnly

      boolean writeOnly()
    • preload

      boolean preload()
    • shared

      boolean shared()
    • transactional

      boolean transactional()
    • maxBatchSize

      int maxBatchSize()
    • segmented

      default boolean segmented()
      Whether or not this store is configured to be segmented. For a non shared store this means there will be a separate instance of each store for each segment. For shared stores normally this means the store is able to do some optimizations based on the segment (ie. select * from table where segment = $1)
      Returns:
      whether this store is configured to be segmented
    • properties

      Properties properties()
    • attributes

      AttributeSet attributes()