Chapter 136. Hazelcast Multimap Component
Available as of Camel version 2.7
The Hazelcast Multimap component is one of Camel Hazelcast Components which allows you to access Hazelcast distributed multimap.
136.1. Options
The Hazelcast Multimap component supports 3 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
| hazelcastInstance (advanced) | The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | HazelcastInstance | |
| hazelcastMode (advanced) | The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. | node | String |
| resolveProperty Placeholders (advanced) | Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. | true | boolean |
The Hazelcast Multimap endpoint is configured using URI syntax:
hazelcast-multimap:cacheName
with the following path and query parameters:
136.1.1. Path Parameters (1 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
| cacheName | Required The name of the cache | String |
136.1.2. Query Parameters (16 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
| defaultOperation (common) | To specify a default operation to use, if no operation header has been provided. | HazelcastOperation | |
| hazelcastInstance (common) | The hazelcast instance reference which can be used for hazelcast endpoint. | HazelcastInstance | |
| hazelcastInstanceName (common) | The hazelcast instance reference name which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. | String | |
| reliable (common) | Define if the endpoint will use a reliable Topic struct or not. | false | boolean |
| bridgeErrorHandler (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. 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. | false | boolean |
| pollingTimeout (consumer) | Define the polling timeout of the Queue consumer in Poll mode | 10000 | long |
| poolSize (consumer) | Define the Pool size for Queue Consumer Executor | 1 | int |
| queueConsumerMode (consumer) | Define the Queue Consumer mode: Listen or Poll | Listen | HazelcastQueueConsumer Mode |
| exceptionHandler (consumer) | 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. | ExceptionHandler | |
| exchangePattern (consumer) | Sets the exchange pattern when the consumer creates an exchange. | ExchangePattern | |
| synchronous (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean |
| concurrentConsumers (seda) | To use concurrent consumers polling from the SEDA queue. | 1 | int |
| onErrorDelay (seda) | Milliseconds before consumer continues polling after an error has occurred. | 1000 | int |
| pollTimeout (seda) | The timeout used when consuming from the SEDA queue. When a timeout occurs, the consumer can check whether it is allowed to continue running. Setting a lower value allows the consumer to react more quickly upon shutdown. | 1000 | int |
| transacted (seda) | If set to true then the consumer runs in transaction mode, where the messages in the seda queue will only be removed if the transaction commits, which happens when the processing is complete. | false | boolean |
| transferExchange (seda) | If set to true the whole Exchange will be transfered. If header or body contains not serializable objects, they will be skipped. | false | boolean |
136.2. Spring Boot Auto-Configuration
The component supports 6 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
| camel.component.hazelcast-multimap.customizer.hazelcast-instance.enabled | Enable or disable the cache-manager customizer. | true | Boolean |
| camel.component.hazelcast-multimap.customizer.hazelcast-instance.override | Configure if the cache manager eventually set on the component should be overridden by the customizer. | false | Boolean |
| camel.component.hazelcast-multimap.enabled | Enable hazelcast-multimap component | true | Boolean |
| camel.component.hazelcast-multimap.hazelcast-instance | The hazelcast instance reference which can be used for hazelcast endpoint. If you don’t specify the instance reference, camel use the default hazelcast instance from the camel-hazelcast instance. The option is a com.hazelcast.core.HazelcastInstance type. | String | |
| camel.component.hazelcast-multimap.hazelcast-mode | The hazelcast mode reference which kind of instance should be used. If you don’t specify the mode, then the node mode will be the default. | node | String |
| camel.component.hazelcast-multimap.resolve-property-placeholders | Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. | true | Boolean |
136.3. multimap cache producer - to("hazelcast-multimap:foo")
A multimap is a cache where you can store n values to one key. The multimap producer provides 4 operations (put, get, removevalue, delete).
Header Variables for the request message:
| Name | Type | Description |
|---|---|---|
|
|
| valid values are: put, get, removevalue, delete From Camel 2.16: clear. |
|
|
| the object id to store / find your object inside the cache |
136.3.1. Sample for put:
Java DSL:
from("direct:put")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.PUT))
.to(String.format("hazelcast-%sbar", HazelcastConstants.MULTIMAP_PREFIX));Spring DSL:
<route>
<from uri="direct:put" />
<log message="put.."/>
<!-- If using version 2.8 and above set headerName to "CamelHazelcastOperationType" -->
<setHeader headerName="hazelcast.operation.type">
<constant>put</constant>
</setHeader>
<to uri="hazelcast-multimap:foo" />
</route>136.3.2. Sample for removevalue:
Java DSL:
from("direct:removevalue")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.REMOVE_VALUE))
.toF("hazelcast-%sbar", HazelcastConstants.MULTIMAP_PREFIX);Spring DSL:
<route>
<from uri="direct:removevalue" />
<log message="removevalue..."/>
<!-- If using version 2.8 and above set headerName to "CamelHazelcastOperationType" -->
<setHeader headerName="hazelcast.operation.type">
<constant>removevalue</constant>
</setHeader>
<to uri="hazelcast-multimap:foo" />
</route>
To remove a value you have to provide the value you want to remove inside the message body. If you have a multimap object \{key: "4711" values: { "my-foo", "my-bar"}} you have to put "my-foo" inside the message body to remove the "my-foo" value.
136.3.3. Sample for get:
Java DSL:
from("direct:get")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.GET))
.toF("hazelcast-%sbar", HazelcastConstants.MULTIMAP_PREFIX)
.to("seda:out");Spring DSL:
<route>
<from uri="direct:get" />
<log message="get.."/>
<!-- If using version 2.8 and above set headerName to "CamelHazelcastOperationType" -->
<setHeader headerName="hazelcast.operation.type">
<constant>get</constant>
</setHeader>
<to uri="hazelcast-multimap:foo" />
<to uri="seda:out" />
</route>136.3.4. Sample for delete:
Java DSL:
from("direct:delete")
.setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.DELETE))
.toF("hazelcast-%sbar", HazelcastConstants.MULTIMAP_PREFIX);Spring DSL:
<route>
<from uri="direct:delete" />
<log message="delete.."/>
<!-- If using version 2.8 and above set headerName to "CamelHazelcastOperationType" -->
<setHeader headerName="hazelcast.operation.type">
<constant>delete</constant>
</setHeader>
<to uri="hazelcast-multimap:foo" />
</route>you can call them in your test class with:
template.sendBodyAndHeader("direct:[put|get|removevalue|delete]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");136.4. multimap cache consumer - from("hazelcast-multimap:foo")
For the multimap cache this component provides the same listeners / variables as for the map cache consumer (except the update and enviction listener). The only difference is the multimap prefix inside the URI. Here is a sample:
fromF("hazelcast-%sbar", HazelcastConstants.MULTIMAP_PREFIX)
.log("object...")
.choice()
.when(header(HazelcastConstants.LISTENER_ACTION).isEqualTo(HazelcastConstants.ADDED))
.log("...added")
.to("mock:added")
//.when(header(HazelcastConstants.LISTENER_ACTION).isEqualTo(HazelcastConstants.ENVICTED))
// .log("...envicted")
// .to("mock:envicted")
.when(header(HazelcastConstants.LISTENER_ACTION).isEqualTo(HazelcastConstants.REMOVED))
.log("...removed")
.to("mock:removed")
.otherwise()
.log("fail!");Header Variables inside the response message:
| Name | Type | Description |
|---|---|---|
|
|
| time of the event in millis |
|
|
| the map consumer sets here "cachelistener" |
|
|
| type of event - here added and removed (and soon envicted) |
|
|
| the oid of the object |
|
|
| the name of the cache - e.g. "foo" |
|
|
| the type of the cache - here multimap |
