Ignite Compute

Run compute operations on an Ignite cluster.

Metadata

Property	Value
Scheme	`ignite-compute`
Support Level	Stable
Labels	cache,clustering
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
`endpointId`	string	✓		The endpoint ID (not used).
`clusterGroupExpression`	object			An expression that returns the Cluster Group for the IgniteCompute instance.
`computeName`	string			The name of the compute job, which will be set via IgniteCompute#withName(String).
`executionType`	object	✓		The compute operation to perform. Possible values: CALL, BROADCAST, APPLY, EXECUTE, RUN, AFFINITY_CALL, AFFINITY_RUN. The component expects different payload types depending on the operation.
`propagateIncomingBodyIfNoReturnValue`	boolean		`true`	Sets whether to propagate the incoming body if the return type of the underlying Ignite operation is void.
`taskName`	string			The task name, only applicable if using the IgniteComputeExecutionType#EXECUTE execution type.
`timeoutMillis`	integer			The timeout interval for triggered jobs, in milliseconds, which will be set via IgniteCompute#withTimeout(long).
`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.