Infinispan Embedded

Read and write from/to Infinispan distributed key/value store and data grid.

Metadata

Property	Value
Scheme	`infinispan-embedded`
Support Level	Stable
Labels	cache,clustering
Version	4.10.2

Maven Dependency

<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-infinispan-embedded</artifactId>
    <version>4.10.2</version>
</dependency>

Endpoint Properties

Name	Type	Required	Default	Description
`cacheName`	string	✓		The name of the cache to use. Use current to use the existing cache name from the currently configured cached manager. Or use default for the default cache manager name.
`queryBuilder`	object			Specifies the query builder.
`clusteredListener`	boolean		`false`	If true, the listener will be installed for the entire cluster
`customListener`	object			Returns the custom listener in use, if provided
`eventTypes`	string			Specifies the set of event types to register by the consumer.Multiple event can be separated by comma. The possible event types are: CACHE_ENTRY_ACTIVATED, CACHE_ENTRY_PASSIVATED, CACHE_ENTRY_VISITED, CACHE_ENTRY_LOADED, CACHE_ENTRY_EVICTED, CACHE_ENTRY_CREATED, CACHE_ENTRY_REMOVED, CACHE_ENTRY_MODIFIED, TRANSACTION_COMPLETED, TRANSACTION_REGISTERED, CACHE_ENTRY_INVALIDATED, CACHE_ENTRY_EXPIRED, DATA_REHASHED, TOPOLOGY_CHANGED, PARTITION_STATUS_CHANGED, PERSISTENCE_AVAILABILITY_CHANGED
`sync`	boolean		`true`	If true, the consumer will receive notifications synchronously
`bridgeErrorHandler`	boolean		`false`	Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.
`exceptionHandler`	object			To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.
`exchangePattern`	object			Sets the exchange pattern when the consumer creates an exchange.
`defaultValue`	object			Set a specific default value for some producer operations
`key`	object			Set a specific key for producer operations
`oldValue`	object			Set a specific old value for some producer operations
`operation`	object		`PUT`	The operation to perform
`value`	object			Set a specific value for producer operations
`lazyStartProducer`	boolean		`false`	Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.
`cacheContainer`	object			Specifies the cache Container to connect
`cacheContainerConfiguration`	object			The CacheContainer configuration. Used if the cacheContainer is not defined.
`configurationUri`	string			An implementation specific URI for the CacheManager
`flags`	string			A comma separated list of org.infinispan.context.Flag to be applied by default on each cache invocation
`remappingFunction`	object			Set a specific remappingFunction to use in a compute operation.
`resultHeader`	string			Store the operation result in a header instead of the message body. By default, resultHeader == null and the query result is stored in the message body, any existing content in the message body is discarded. If resultHeader is set, the value is used as the name of the header to store the query result and the original message body is preserved. This value can be overridden by an in message header named: CamelInfinispanOperationResultHeader