Ignite Queues

Interact with Ignite Queue data structures.

Metadata

Property	Value
Scheme	`ignite-queue`
Support Level	Stable
Labels	cache,clustering,messaging
Version	4.10.2

Maven Dependency

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

Endpoint Properties

Name	Type	Required	Default	Description
`name`	string	✓		The queue name.
`capacity`	integer			The queue capacity. Default: non-bounded.
`configuration`	object			The collection configuration. Default: empty configuration. You can also conveniently set inner properties by using configuration.xyz=123 options.
`operation`	object			The operation to invoke on the Ignite Queue. Superseded by the IgniteConstants.IGNITE_QUEUE_OPERATION header in the IN message. Possible values: CONTAINS, ADD, SIZE, REMOVE, ITERATOR, CLEAR, RETAIN_ALL, ARRAY, DRAIN, ELEMENT, PEEK, OFFER, POLL, TAKE, PUT.
`propagateIncomingBodyIfNoReturnValue`	boolean		`true`	Sets whether to propagate the incoming body if the return type of the underlying Ignite operation is void.
`timeoutMillis`	integer			The queue timeout in milliseconds. Default: no timeout.
`treatCollectionsAsCacheObjects`	boolean		`false`	Sets whether to treat Collections as cache objects or as Collections of items to insert/update/compute, etc.
`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.