urn:infinispan:config:store:jdbc:9.1

string-keyed-jdbc-store

NameTypeDefaultDescription
key-to-string-mapperstring The class name of a org.infinispan.persistence.keymappers.Key2StringMapper to use for mapping keys to strings suitable for storage in a database table. Defaults to org.infinispan.persistence.keymappers.DefaultTwoWayKey2StringMapper

string-keyed-table?

Defines the table used to store cache entries.

NameTypeDefaultDescription
prefixstringispn_entryDefines the prefix prepended to the cache name used when composing the name of the cache entry table.
NameTypeDefaultDescription
fetch-sizeint100The fetch size used when querying from this table. Used to avoid heap memory exhaustion when query is large.
batch-sizeint100Deprecated, use the max-batch-size store property instead. The statement batch size used when modifying this table.
create-on-startbooleantrueDetermines whether database tables should be created by the store on startup.
drop-on-exitbooleanfalseDetermines whether database tables should be dropped by the store on shutdown.

id-column?

Defines the column in which to store the cache key or bucket id.

NameTypeDefaultDescription
namestringidThe name of the column used to store the cache key or bucket id.
typestringVARCHARThe type of the column used to store the cache key or bucket id.

data-column?

Defines the column in which to store the cache entry or bucket.

NameTypeDefaultDescription
namestringdatumThe name of the column used to store the cache entry or bucket.
typestringBINARYThe type of the column used to store the cache entry or bucket.

timestamp-column?

Defines the column in which to store the timestamp of the cache entry or bucket.

NameTypeDefaultDescription
namestringversionThe name of the column used to store the cache entry or bucket timestamp.
typestringBIGINTThe type of the column used to store the cache entry or bucket timestamp.
NameTypeDefaultDescription
dialect
ACCESS
DB2
DB2_390
DERBY
FIREBIRD
H2
HSQL
INFORMIX
INTERBASE
MARIA_DB
MYSQL
ORACLE
POSTGRES
SQL_SERVER
SQLITE
SYBASE
Defines the JDBC dialect.
db-major-versionnonNegativeIntegerDefines the major version of the database.
db-minor-versionnonNegativeIntegerDefines the minor version of the database.

connection-pool

NameTypeDefaultDescription
properties-filestring The path of a properties file that provides additional configuration for the connection pool.
connection-urlstring A JDBC driver-specific connection URL
driverstring The class name of the driver used for connecting to the database.
passwordstring The password to use when connecting via connectionUrl
usernamestring The username to use when connecting via connectionUrl

data-source

NameTypeDefaultDescription
jndi-urlstring The address of a datasource to use when connecting

simple-connection

NameTypeDefaultDescription
connection-urlstring A JDBC driver-specific connection URL
driverstring The class name of the driver used for connecting to the database.
passwordstring The password to use when connecting via connectionUrl
usernamestring The username to use when connecting via connectionUrl
NameTypeDefaultDescription
sharedbooleanfalseThis setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
transactionalbooleanfalseThis setting should be set to true when the underlying cache store supports transactions and it is desirable for the underlying store and the cache to remain synchronized. With this enabled any Exceptions thrown whilst writing to the underlying store will result in both the store's and cache's transactions rollingback.
preloadbooleanfalseIf true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
fetch-statebooleanfalseIf true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
purgebooleanfalseIf true, purges this cache store when it starts up.
singletonbooleanfalseIf true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store. Deprecated: A shared store should be used instead, as this limits store writes to the primary owner of a key
read-onlybooleanfalseIf true, the cache store will only be used to load entries. Any modifications made to the caches will not be applied to the store.
max-batch-sizeint100The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.

write-behind?

Configures a cache store as write-behind instead of write-through.

NameTypeDefaultDescription
modification-queue-sizeint1024 Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through. until it can accept new entries
thread-pool-sizeint1 Size of the thread pool whose threads are responsible for applying the modifications to the cache store.

property*

A cache store property with name and value.

Expand/Collapse All