Cache storage adapter with parallel loading in LoadAll method.
Cache storage convenience adapter. It provides default implementation for
bulk operations, such as
RemoveAll by sequentially calling corresponding
Remove operations. Use this adapter whenever
such behaviour is acceptable. However in many cases it maybe more preferable
to take advantage of database batch update functionality, and therefore default
adapter implementation may not be the best option.
LoadCache method has empty implementation because it is
essentially up to the user to invoke it with specific arguments.
Indicates an error during CacheStore operation.
API for cache persistent storage for read-through and write-through behavior.
Generic argument types depend on KeepBinaryInStore property.
true (default), cache store operates on IBinaryObject instances.
Otherwise, generic arguments should be the same as in corresponding ICache<TK, TV>.
Persistent store is configured in Ignite's Spring XML configuration file via
CacheConfiguration.setStore() property. If you have an implementation
of cache store in .NET, you should use special Java wrapper which accepts assembly name and
class name of .NET store implementation (both properties are mandatory).
Optionally, you may specify "properies" property to set any property values on an instance of your store.
<property name="assemblyName" value="MyAssembly"/>
<property name="className" value="MyApp.MyCacheStore"/>
<entry key="StringProperty" value="String value"/>
All transactional operations of this API are provided with ongoing ITransaction,
if any. You can attach any metadata to transaction, e.g. to recognize if several operations
belong to the same transaction or not.
OdbcConnection conn = tx.Meta("some.name");
if (conn == null)
conn = ...; // Create or get connection.
// Store connection in transaction metadata, so it can be accessed
// for other operations on the same transaction.
Session for the cache store operations. The main purpose of cache store session is to hold context between multiple store invocations whenever in transaction. For example, you can save current database connection in the session Properties map. You can then commit this connection in the SessionEnd(Boolean) method.