docs/components/modules/ROOT/pages/hazelcast-map-component.adoc - camel - Git at Google

 [[hazelcast-map-component]]
 = Hazelcast Map Component
 //THIS FILE IS COPIED: EDIT THE SOURCE FILE:
 :page-source: components/camel-hazelcast/src/main/docs/hazelcast-map-component.adoc
 :docTitle: Hazelcast Map
 :artifactId: camel-hazelcast
 :description: Perform operations on Hazelcast distributed map.
 :since: 2.7
 :supportLevel: Stable
 :component-header: Both producer and consumer are supported
 //Manually maintained attributes
 :group: Hazelcast

 *Since Camel {since}*

 *{component-header}*

 The http://www.hazelcast.com/[Hazelcast] Map component is one of Camel Hazelcast Components which allows you to access Hazelcast distributed map.


 == Options

 // component options: START
 The Hazelcast Map component supports 5 options, which are listed below.


 [width="100%",cols="2,5,^1,2",options="header"]
 |===
 | Name | Description | Default | Type
 | *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
 | *lazyStartProducer* (producer) | 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. | false | boolean
 | *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
 | *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
 |===
 // component options: END
 // endpoint options: START
 The Hazelcast Map endpoint is configured using URI syntax:

 ----
 hazelcast-map:cacheName
 ----

 with the following path and query parameters:

 === Path Parameters (1 parameters):


 [width="100%",cols="2,5,^1,2",options="header"]
 |===
 | Name | Description | Default | Type
 | *cacheName* | *Required* The name of the cache |  | String
 |===


 === Query Parameters (9 parameters):


 [width="100%",cols="2,5,^1,2",options="header"]
 |===
 | Name | Description | Default | Type
 | *defaultOperation* (common) | To specify a default operation to use, if no operation header has been provided. The value can be one of: put, delete, get, update, query, getAll, clear, putIfAbsent, allAll, removeAll, retainAll, evict, evictAll, valueCount, containsKey, containsValue, keySet, removevalue, increment, decrement, setvalue, destroy, compareAndSet, getAndAdd, add, offer, peek, poll, remainingCapacity, drainTo, removeIf, take, publish, readOnceHeal, readOnceTail, capacity |  | 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
 | *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
 | *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. The value can be one of: InOnly, InOut, InOptionalOut |  | ExchangePattern
 | *lazyStartProducer* (producer) | 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. | false | boolean
 | *basicPropertyBinding* (advanced) | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
 | *synchronous* (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean
 |===
 // endpoint options: END


 == Map cache producer - to("hazelcast-map:foo")

 If you want to store a value in a map you can use the map cache
 producer.

 The map cache producer provides follow operations specified by *CamelHazelcastOperationType* header:

 * put
 * putIfAbsent
 * get
 * getAll
 * keySet
 * containsKey
 * containsValue
 * delete
 * update
 * query
 * clear
 * evict
 * evictAll

 All operations are provide the inside the "hazelcast.operation.type" header variable. In Java
 DSL you can use the constants from `org.apache.camel.component.hazelcast.HazelcastOperation`.

 Header Variables for the request message:

 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
 |Name |Type |Description
 |`CamelHazelcastOperationType` |`String` | as already described.

 |`CamelHazelcastObjectId` |`String` |the object id to store / find your object inside the cache (not needed for the query operation)
 |=======================================================================

 *put* and *putIfAbsent* operations provide an eviction mechanism:

 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
 |Name |Type |Description
 |`CamelHazelcastObjectTtlValue` |`Integer` | value of TTL.

 |`CamelHazelcastObjectTtlUnit` |`java.util.concurrent.TimeUnit` | value of time unit ( DAYS / HOURS / MINUTES / ....
 |=======================================================================

 You can call the samples with:

 [source,java]
 -------------------------------------------------------------------------------------------------------------------
 template.sendBodyAndHeader("direct:[put|get|update|delete|query|evict]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");
 -------------------------------------------------------------------------------------------------------------------

 === Sample for *put*:

 Java DSL:

 [source,java]
 ------------------------------------------------------------------------------------
 from("direct:put")
 .setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.PUT))
 .toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX);
 ------------------------------------------------------------------------------------

 Spring DSL:

 [source,java]
 -----------------------------------------------------------------------------------------------
 <route>
     <from uri="direct:put" />
     <setHeader name="hazelcast.operation.type">
         <constant>put</constant>
     </setHeader>
     <to uri="hazelcast-map:foo" />
 </route>
 -----------------------------------------------------------------------------------------------

 Sample for *put* with eviction:

 Java DSL:

 [source,java]
 ------------------------------------------------------------------------------------
 from("direct:put")
 .setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.PUT))
 .setHeader(HazelcastConstants.TTL_VALUE, constant(Long.valueOf(1)))
 .setHeader(HazelcastConstants.TTL_UNIT, constant(TimeUnit.MINUTES))
 .toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX);
 ------------------------------------------------------------------------------------

 Spring DSL:

 [source,java]
 -----------------------------------------------------------------------------------------------
 <route>
     <from uri="direct:put" />
     <setHeader name="hazelcast.operation.type">
         <constant>put</constant>
     </setHeader>
     <setHeader name="HazelcastConstants.TTL_VALUE">
         <simple resultType="java.lang.Long">1</simple>
     </setHeader>
     <setHeader name="HazelcastConstants.TTL_UNIT">
         <simple resultType="java.util.concurrent.TimeUnit">TimeUnit.MINUTES</simple>
     </setHeader>
     <to uri="hazelcast-map:foo" />
 </route>
 -----------------------------------------------------------------------------------------------


 === Sample for *get*:

 Java DSL:

 [source,java]
 ------------------------------------------------------------------------------------
 from("direct:get")
 .setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.GET))
 .toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX)
 .to("seda:out");
 ------------------------------------------------------------------------------------

 Spring DSL:

 [source,java]
 -----------------------------------------------------------------------------------------------
 <route>
     <from uri="direct:get" />
     <setHeader name="hazelcast.operation.type">
         <constant>get</constant>
     </setHeader>
     <to uri="hazelcast-map:foo" />
     <to uri="seda:out" />
 </route>
 -----------------------------------------------------------------------------------------------

 === Sample for *update*:

 Java DSL:

 [source,java]
 ---------------------------------------------------------------------------------------
 from("direct:update")
 .setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.UPDATE))
 .toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX);
 ---------------------------------------------------------------------------------------

 Spring DSL:

 [source,java]
 -----------------------------------------------------------------------------------------------
 <route>
     <from uri="direct:update" />
     <setHeader name="hazelcast.operation.type">
         <constant>update</constant>
     </setHeader>
     <to uri="hazelcast-map:foo" />
 </route>
 -----------------------------------------------------------------------------------------------

 === Sample for *delete*:

 Java DSL:

 [source,java]
 ---------------------------------------------------------------------------------------
 from("direct:delete")
 .setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.DELETE))
 .toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX);
 ---------------------------------------------------------------------------------------

 Spring DSL:

 [source,java]
 -----------------------------------------------------------------------------------------------
 <route>
     <from uri="direct:delete" />
     <setHeader name="hazelcast.operation.type">
         <constant>delete</constant>
     </setHeader>
     <to uri="hazelcast-map:foo" />
 </route>
 -----------------------------------------------------------------------------------------------

 === Sample for *query*

 Java DSL:

 [source,java]
 --------------------------------------------------------------------------------------
 from("direct:query")
 .setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.QUERY))
 .toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX)
 .to("seda:out");
 --------------------------------------------------------------------------------------

 Spring DSL:

 [source,java]
 -----------------------------------------------------------------------------------------------
 <route>
     <from uri="direct:query" />
     <setHeader name="hazelcast.operation.type">
         <constant>query</constant>
     </setHeader>
     <to uri="hazelcast-map:foo" />
     <to uri="seda:out" />
 </route>
 -----------------------------------------------------------------------------------------------

 For the query operation Hazelcast offers a SQL like syntax to query your
 distributed map.

 [source,java]
 -------------------------------------------------------------------------------
 String q1 = "bar > 1000";
 template.sendBodyAndHeader("direct:query", null, HazelcastConstants.QUERY, q1);
 -------------------------------------------------------------------------------


 == Map cache consumer - from("hazelcast-map:foo")

 Hazelcast provides event listeners on their data grid. If you want to be
 notified if a cache will be manipulated, you can use the map consumer.
 There're 4 events: *put*, *update*, *delete* and *envict*. The event
 type will be stored in the "*hazelcast.listener.action*" header
 variable. The map consumer provides some additional information inside
 these variables:

 Header Variables inside the response message:

 [width="100%",cols="10%,10%,80%",options="header",]
 |=======================================================================
 |Name |Type |Description

 |`CamelHazelcastListenerTime` |`Long` |time of the event in millis

 |`CamelHazelcastListenerType` |`String` |the map consumer sets here "cachelistener"

 |`CamelHazelcastListenerAction` |`String` |type of event - here *added*, *updated*, *envicted* and *removed*.

 |`CamelHazelcastObjectId` |`String` |the oid of the object

 |`CamelHazelcastCacheName` |`String` |the name of the cache - e.g. "foo"

 |`CamelHazelcastCacheType` |`String` |the type of the cache - here map
 |=======================================================================

 The object value will be stored within *put* and *update* actions inside
 the message body.

 Here's a sample:

 [source,java]
 --------------------------------------------------------------------------------------------
 fromF("hazelcast-%sfoo", HazelcastConstants.MAP_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.UPDATED))
          .log("...updated")
          .to("mock:updated")
     .when(header(HazelcastConstants.LISTENER_ACTION).isEqualTo(HazelcastConstants.REMOVED))
          .log("...removed")
          .to("mock:removed")
     .otherwise()
          .log("fail!");
 --------------------------------------------------------------------------------------------

 include::camel-spring-boot::page$hazelcast-starter.adoc[]
	[[hazelcast-map-component]]
	= Hazelcast Map Component
	//THIS FILE IS COPIED: EDIT THE SOURCE FILE:
	:page-source: components/camel-hazelcast/src/main/docs/hazelcast-map-component.adoc
	:docTitle: Hazelcast Map
	:artifactId: camel-hazelcast
	:description: Perform operations on Hazelcast distributed map.
	:since: 2.7
	:supportLevel: Stable
	:component-header: Both producer and consumer are supported
	//Manually maintained attributes
	:group: Hazelcast

	Since Camel {since}

	{component-header}

	The http://www.hazelcast.com/[Hazelcast] Map component is one of Camel Hazelcast Components which allows you to access Hazelcast distributed map.


	== Options

	// component options: START
	The Hazelcast Map component supports 5 options, which are listed below.



	[width="100%",cols="2,5,^1,2",options="header"]
	\|===
	\| Name \| Description \| Default \| Type
	\| 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
	\| lazyStartProducer (producer) \| 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. \| false \| boolean
	\| basicPropertyBinding (advanced) \| Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities \| false \| boolean
	\| 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
	\|===
	// component options: END
	// endpoint options: START
	The Hazelcast Map endpoint is configured using URI syntax:

	----
	hazelcast-map:cacheName
	----

	with the following path and query parameters:

	=== Path Parameters (1 parameters):


	[width="100%",cols="2,5,^1,2",options="header"]
	\|===
	\| Name \| Description \| Default \| Type
	\| cacheName \| Required The name of the cache \| \| String
	\|===


	=== Query Parameters (9 parameters):


	[width="100%",cols="2,5,^1,2",options="header"]
	\|===
	\| Name \| Description \| Default \| Type
	\| defaultOperation (common) \| To specify a default operation to use, if no operation header has been provided. The value can be one of: put, delete, get, update, query, getAll, clear, putIfAbsent, allAll, removeAll, retainAll, evict, evictAll, valueCount, containsKey, containsValue, keySet, removevalue, increment, decrement, setvalue, destroy, compareAndSet, getAndAdd, add, offer, peek, poll, remainingCapacity, drainTo, removeIf, take, publish, readOnceHeal, readOnceTail, capacity \| \| 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
	\| 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
	\| 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. The value can be one of: InOnly, InOut, InOptionalOut \| \| ExchangePattern
	\| lazyStartProducer (producer) \| 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. \| false \| boolean
	\| basicPropertyBinding (advanced) \| Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities \| false \| boolean
	\| synchronous (advanced) \| Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). \| false \| boolean
	\|===
	// endpoint options: END




	== Map cache producer - to("hazelcast-map:foo")

	If you want to store a value in a map you can use the map cache
	producer.

	The map cache producer provides follow operations specified by CamelHazelcastOperationType header:

	* put
	* putIfAbsent
	* get
	* getAll
	* keySet
	* containsKey
	* containsValue
	* delete
	* update
	* query
	* clear
	* evict
	* evictAll

	All operations are provide the inside the "hazelcast.operation.type" header variable. In Java
	DSL you can use the constants from `org.apache.camel.component.hazelcast.HazelcastOperation`.

	Header Variables for the request message:

	[width="100%",cols="10%,10%,80%",options="header",]
	\|=======================================================================
	\|Name \|Type \|Description
	\|`CamelHazelcastOperationType` \|`String` \| as already described.

	\|`CamelHazelcastObjectId` \|`String` \|the object id to store / find your object inside the cache (not needed for the query operation)
	\|=======================================================================

	put and putIfAbsent operations provide an eviction mechanism:

	[width="100%",cols="10%,10%,80%",options="header",]
	\|=======================================================================
	\|Name \|Type \|Description
	\|`CamelHazelcastObjectTtlValue` \|`Integer` \| value of TTL.

	\|`CamelHazelcastObjectTtlUnit` \|`java.util.concurrent.TimeUnit` \| value of time unit ( DAYS / HOURS / MINUTES / ....
	\|=======================================================================

	You can call the samples with:

	[source,java]
	-------------------------------------------------------------------------------------------------------------------
	template.sendBodyAndHeader("direct:[put\|get\|update\|delete\|query\|evict]", "my-foo", HazelcastConstants.OBJECT_ID, "4711");
	-------------------------------------------------------------------------------------------------------------------

	=== Sample for put:

	Java DSL:

	[source,java]
	------------------------------------------------------------------------------------
	from("direct:put")
	.setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.PUT))
	.toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX);
	------------------------------------------------------------------------------------

	Spring DSL:

	[source,java]
	-----------------------------------------------------------------------------------------------
	<route>
	<from uri="direct:put" />
	<setHeader name="hazelcast.operation.type">
	<constant>put</constant>
	</setHeader>
	<to uri="hazelcast-map:foo" />
	</route>
	-----------------------------------------------------------------------------------------------

	Sample for put with eviction:

	Java DSL:

	[source,java]
	------------------------------------------------------------------------------------
	from("direct:put")
	.setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.PUT))
	.setHeader(HazelcastConstants.TTL_VALUE, constant(Long.valueOf(1)))
	.setHeader(HazelcastConstants.TTL_UNIT, constant(TimeUnit.MINUTES))
	.toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX);
	------------------------------------------------------------------------------------

	Spring DSL:

	[source,java]
	-----------------------------------------------------------------------------------------------
	<route>
	<from uri="direct:put" />
	<setHeader name="hazelcast.operation.type">
	<constant>put</constant>
	</setHeader>
	<setHeader name="HazelcastConstants.TTL_VALUE">
	<simple resultType="java.lang.Long">1</simple>
	</setHeader>
	<setHeader name="HazelcastConstants.TTL_UNIT">
	<simple resultType="java.util.concurrent.TimeUnit">TimeUnit.MINUTES</simple>
	</setHeader>
	<to uri="hazelcast-map:foo" />
	</route>
	-----------------------------------------------------------------------------------------------


	=== Sample for get:

	Java DSL:

	[source,java]
	------------------------------------------------------------------------------------
	from("direct:get")
	.setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.GET))
	.toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX)
	.to("seda:out");
	------------------------------------------------------------------------------------

	Spring DSL:

	[source,java]
	-----------------------------------------------------------------------------------------------
	<route>
	<from uri="direct:get" />
	<setHeader name="hazelcast.operation.type">
	<constant>get</constant>
	</setHeader>
	<to uri="hazelcast-map:foo" />
	<to uri="seda:out" />
	</route>
	-----------------------------------------------------------------------------------------------

	=== Sample for update:

	Java DSL:

	[source,java]
	---------------------------------------------------------------------------------------
	from("direct:update")
	.setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.UPDATE))
	.toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX);
	---------------------------------------------------------------------------------------

	Spring DSL:

	[source,java]
	-----------------------------------------------------------------------------------------------
	<route>
	<from uri="direct:update" />
	<setHeader name="hazelcast.operation.type">
	<constant>update</constant>
	</setHeader>
	<to uri="hazelcast-map:foo" />
	</route>
	-----------------------------------------------------------------------------------------------

	=== Sample for delete:

	Java DSL:

	[source,java]
	---------------------------------------------------------------------------------------
	from("direct:delete")
	.setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.DELETE))
	.toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX);
	---------------------------------------------------------------------------------------

	Spring DSL:

	[source,java]
	-----------------------------------------------------------------------------------------------
	<route>
	<from uri="direct:delete" />
	<setHeader name="hazelcast.operation.type">
	<constant>delete</constant>
	</setHeader>
	<to uri="hazelcast-map:foo" />
	</route>
	-----------------------------------------------------------------------------------------------

	=== Sample for query

	Java DSL:

	[source,java]
	--------------------------------------------------------------------------------------
	from("direct:query")
	.setHeader(HazelcastConstants.OPERATION, constant(HazelcastOperation.QUERY))
	.toF("hazelcast-%sfoo", HazelcastConstants.MAP_PREFIX)
	.to("seda:out");
	--------------------------------------------------------------------------------------

	Spring DSL:

	[source,java]
	-----------------------------------------------------------------------------------------------
	<route>
	<from uri="direct:query" />
	<setHeader name="hazelcast.operation.type">
	<constant>query</constant>
	</setHeader>
	<to uri="hazelcast-map:foo" />
	<to uri="seda:out" />
	</route>
	-----------------------------------------------------------------------------------------------

	For the query operation Hazelcast offers a SQL like syntax to query your
	distributed map.

	[source,java]
	-------------------------------------------------------------------------------
	String q1 = "bar > 1000";
	template.sendBodyAndHeader("direct:query", null, HazelcastConstants.QUERY, q1);
	-------------------------------------------------------------------------------


	== Map cache consumer - from("hazelcast-map:foo")

	Hazelcast provides event listeners on their data grid. If you want to be
	notified if a cache will be manipulated, you can use the map consumer.
	There're 4 events: put, update, delete and envict. The event
	type will be stored in the "hazelcast.listener.action" header
	variable. The map consumer provides some additional information inside
	these variables:

	Header Variables inside the response message:

	[width="100%",cols="10%,10%,80%",options="header",]
	\|=======================================================================
	\|Name \|Type \|Description

	\|`CamelHazelcastListenerTime` \|`Long` \|time of the event in millis

	\|`CamelHazelcastListenerType` \|`String` \|the map consumer sets here "cachelistener"

	\|`CamelHazelcastListenerAction` \|`String` \|type of event - here added, updated, envicted and removed.

	\|`CamelHazelcastObjectId` \|`String` \|the oid of the object

	\|`CamelHazelcastCacheName` \|`String` \|the name of the cache - e.g. "foo"

	\|`CamelHazelcastCacheType` \|`String` \|the type of the cache - here map
	\|=======================================================================

	The object value will be stored within put and update actions inside
	the message body.

	Here's a sample:

	[source,java]
	--------------------------------------------------------------------------------------------
	fromF("hazelcast-%sfoo", HazelcastConstants.MAP_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.UPDATED))
	.log("...updated")
	.to("mock:updated")
	.when(header(HazelcastConstants.LISTENER_ACTION).isEqualTo(HazelcastConstants.REMOVED))
	.log("...removed")
	.to("mock:removed")
	.otherwise()
	.log("fail!");
	--------------------------------------------------------------------------------------------

	include::camel-spring-boot::page$hazelcast-starter.adoc[]