camel-ignite-cache-kafka-connector source configuration
Connector Description: Perform cache operations on an Ignite cache or consume changes from a continuous query.
When using camel-ignite-cache-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
<dependency>
<groupId>org.apache.camel.kafkaconnector</groupId>
<artifactId>camel-ignite-cache-kafka-connector</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel Kafka connector version -->
</dependency>
To use this source connector in Kafka connect you’ll need to set the following connector.class
connector.class=org.apache.camel.kafkaconnector.ignitecache.CamelIgnitecacheSourceConnector
The camel-ignite-cache source connector supports 18 options, which are listed below.
Name | Description | Default | Priority |
---|---|---|---|
Required The cache name. |
HIGH |
||
Sets whether to propagate the incoming body if the return type of the underlying Ignite operation is void. |
true |
MEDIUM |
|
Sets whether to treat Collections as cache objects or as Collections of items to insert/update/compute, etc. |
false |
MEDIUM |
|
Whether auto unsubscribe is enabled in the Continuous Query Consumer. Default value notice: ContinuousQuery.DFLT_AUTO_UNSUBSCRIBE. |
true |
MEDIUM |
|
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
MEDIUM |
|
Whether to process existing results that match the query. Used on initialization of the Continuous Query Consumer. |
false |
MEDIUM |
|
Whether to pack each update in an individual Exchange, even if multiple updates are received in one batch. Only used by the Continuous Query Consumer. |
true |
MEDIUM |
|
The page size. Only used by the Continuous Query Consumer. Default value notice: ContinuousQuery.DFLT_PAGE_SIZE. |
1 |
MEDIUM |
|
The Query to execute, only needed for operations that require it, and for the Continuous Query Consumer. |
MEDIUM |
||
The remote filter, only used by the Continuous Query Consumer. |
MEDIUM |
||
The time interval for the Continuous Query Consumer. Default value notice: ContinuousQuery.DFLT_TIME_INTERVAL. |
0L |
MEDIUM |
|
To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
MEDIUM |
||
Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]. Enum values:
|
MEDIUM |
||
The resource from where to load the configuration. It can be a: URL, String or InputStream type. |
MEDIUM |
||
To use an existing Ignite instance. |
MEDIUM |
||
Allows the user to set a programmatic ignite configuration. |
MEDIUM |
||
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
MEDIUM |
|
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 |
MEDIUM |
The camel-ignite-cache source connector has no converters out of the box.
The camel-ignite-cache source connector has no transforms out of the box.
The camel-ignite-cache source connector has no aggregation strategies out of the box.