camel-ignite-queue-kafka-connector sink configuration

When using camel-ignite-queue-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-queue-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.ignitequeue.CamelIgnitequeueSinkConnector

The camel-ignite-queue sink connector supports 15 options, which are listed below.

Name	Description	Default	Required	Priority
camel.sink.path.name	The queue name.	null	true	HIGH
camel.sink.endpoint.capacity	The queue capacity. Default: non-bounded.	null	false	MEDIUM
camel.sink.endpoint.configuration	The collection configuration. Default: empty configuration. You can also conveniently set inner properties by using configuration.xyz=123 options.	null	false	MEDIUM
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	false	MEDIUM
camel.sink.endpoint.operation	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. One of: [CONTAINS] [ADD] [SIZE] [REMOVE] [ITERATOR] [CLEAR] [RETAIN_ALL] [ARRAY] [DRAIN] [ELEMENT] [PEEK] [OFFER] [POLL] [TAKE] [PUT]	null	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	false	MEDIUM
camel.sink.endpoint.timeoutMillis	The queue timeout in milliseconds. Default: no timeout.	null	false	MEDIUM
camel.sink.endpoint.treatCollectionsAsCacheObjects	Sets whether to treat Collections as cache objects or as Collections of items to insert/update/compute, etc.	false	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	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	false	MEDIUM
camel.component.ignite-queue.configurationResource	The resource from where to load the configuration. It can be a: URL, String or InputStream type.	null	false	MEDIUM
camel.component.ignite-queue.ignite	To use an existing Ignite instance.	null	false	MEDIUM
camel.component.ignite-queue.igniteConfiguration	Allows the user to set a programmatic ignite configuration.	null	false	MEDIUM
camel.component.ignite-queue.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	false	MEDIUM
camel.component.ignite-queue.basicPropertyBinding	Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities	false	false	LOW

Name

Description

Default

Required

Priority

camel.sink.path.name

The queue name.

null

true

HIGH

camel.sink.endpoint.capacity

The queue capacity. Default: non-bounded.

null

false

MEDIUM

camel.sink.endpoint.configuration

The collection configuration. Default: empty configuration. You can also conveniently set inner properties by using configuration.xyz=123 options.

null

false

MEDIUM

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.operation

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. One of: [CONTAINS] [ADD] [SIZE] [REMOVE] [ITERATOR] [CLEAR] [RETAIN_ALL] [ARRAY] [DRAIN] [ELEMENT] [PEEK] [OFFER] [POLL] [TAKE] [PUT]

null

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

false

MEDIUM

camel.sink.endpoint.timeoutMillis

The queue timeout in milliseconds. Default: no timeout.

null

false

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-queue.configurationResource

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

null

false

MEDIUM

camel.component.ignite-queue.ignite

To use an existing Ignite instance.

null

false

MEDIUM

camel.component.ignite-queue.igniteConfiguration

Allows the user to set a programmatic ignite configuration.

null

false

MEDIUM

camel.component.ignite-queue.lazyStartProducer

false

MEDIUM

camel.component.ignite-queue.basicPropertyBinding

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

false

LOW

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

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

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