camel-ignite-compute-kafka-connector sink configuration

When using camel-ignite-compute-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:

<dependency>
  <groupId>org.apache.camel.kafkaconnector</groupId>
  <artifactId>camel-ignite-compute-kafka-connector</artifactId>
  <version>x.x.x</version>
  <!-- use the same version as your Camel Kafka connector version -->
</dependency>

To use this Sink connector in Kafka connect you’ll need to set the following connector.class

connector.class=org.apache.camel.kafkaconnector.ignitecompute.CamelIgnitecomputeSinkConnector

The camel-ignite-compute sink connector supports 16 options, which are listed below.

Name Description Default Priority

camel.sink.path.endpointId

The endpoint ID (not used).

null

HIGH

camel.sink.endpoint.clusterGroupExpression

An expression that returns the Cluster Group for the IgniteCompute instance.

null

MEDIUM

camel.sink.endpoint.computeName

The name of the compute job, which will be set via IgniteCompute#withName(String).

null

MEDIUM

camel.sink.endpoint.executionType

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. One of: [CALL] [BROADCAST] [APPLY] [EXECUTE] [RUN] [AFFINITY_CALL] [AFFINITY_RUN]

null

HIGH

camel.sink.endpoint.lazyStartProducer

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

MEDIUM

camel.sink.endpoint.propagateIncomingBodyIfNo ReturnValue

Sets whether to propagate the incoming body if the return type of the underlying Ignite operation is void.

true

MEDIUM

camel.sink.endpoint.taskName

The task name, only applicable if using the IgniteComputeExecutionType#EXECUTE execution type.

null

MEDIUM

camel.sink.endpoint.timeoutMillis

The timeout interval for triggered jobs, in milliseconds, which will be set via IgniteCompute#withTimeout(long).

null

MEDIUM

camel.sink.endpoint.treatCollectionsAsCacheObjects

Sets whether to treat Collections as cache objects or as Collections of items to insert/update/compute, etc.

false

MEDIUM

camel.sink.endpoint.basicPropertyBinding

Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities

false

MEDIUM

camel.sink.endpoint.synchronous

Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).

false

MEDIUM

camel.component.ignite-compute.configuration Resource

The resource from where to load the configuration. It can be a: URL, String or InputStream type.

null

MEDIUM

camel.component.ignite-compute.ignite

To use an existing Ignite instance.

null

MEDIUM

camel.component.ignite-compute.igniteConfiguration

Allows the user to set a programmatic ignite configuration.

null

MEDIUM

camel.component.ignite-compute.lazyStartProducer

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

MEDIUM

camel.component.ignite-compute.basicProperty Binding

Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities

false

MEDIUM

The camel-ignite-compute sink connector has no converters out of the box.

The camel-ignite-compute sink connector has no transforms out of the box.

The camel-ignite-compute sink connector has no aggregation strategies out of the box.