camel-ignite-messaging-kafka-connector sink configuration
Connector Description: Send and receive messages from an Ignite topic.
When using camel-ignite-messaging-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-messaging-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.ignitemessaging.CamelIgnitemessagingSinkConnectorThe camel-ignite-messaging sink connector supports 12 options, which are listed below.
| Name | Description | Default | Required | Priority |
|---|---|---|---|---|
camel.sink.path.topic |
The topic name. |
null |
true |
HIGH |
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.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.clusterGroupExpression |
The cluster group expression. |
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.sendMode |
The send mode to use. Possible values: UNORDERED, ORDERED. One of: [ORDERED] [UNORDERED] |
"UNORDERED" |
false |
MEDIUM |
camel.sink.endpoint.timeout |
The timeout for the send operation when using ordered messages. |
null |
false |
MEDIUM |
camel.component.ignite-messaging.configuration Resource |
The resource from where to load the configuration. It can be a: URL, String or InputStream type. |
null |
false |
MEDIUM |
camel.component.ignite-messaging.ignite |
To use an existing Ignite instance. |
null |
false |
MEDIUM |
camel.component.ignite-messaging.ignite Configuration |
Allows the user to set a programmatic ignite configuration. |
null |
false |
MEDIUM |
camel.component.ignite-messaging.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-messaging.autowiredEnabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
false |
MEDIUM |
The camel-ignite-messaging sink connector has no converters out of the box.
The camel-ignite-messaging sink connector has no transforms out of the box.
The camel-ignite-messaging sink connector has no aggregation strategies out of the box.