// kafka-connector options: START
[[camel-ignite-messaging-kafka-connector-source]]
= camel-ignite-messaging-kafka-connector source configuration

Connector description: Send and receive messages from an Ignite topic.

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

[source,xml]
----
<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 Source connector in Kafka connect you'll need to set the following connector.class

[source,java]
----
connector.class=org.apache.camel.kafkaconnector.ignitemessaging.CamelIgnitemessagingSourceConnector
----


The camel-ignite-messaging source connector supports 12 options, which are listed below.



[width="100%",cols="2,5,^1,1,1",options="header"]
|===
| Name | Description | Default | Required | Priority
| *camel.source.path.topic* | The topic name. | null | true | HIGH
| *camel.source.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.source.endpoint.treatCollectionsAsCache Objects* | Sets whether to treat Collections as cache objects or as Collections of items to insert/update/compute, etc. | false | false | MEDIUM
| *camel.source.endpoint.bridgeErrorHandler* | 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 | false | MEDIUM
| *camel.source.endpoint.exceptionHandler* | 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. | null | false | MEDIUM
| *camel.source.endpoint.exchangePattern* | Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut] | null | false | MEDIUM
| *camel.source.endpoint.clusterGroupExpression* | The cluster group expression. | 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.bridgeError Handler* | 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 | 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 source connector has no converters out of the box.





The camel-ignite-messaging source connector has no transforms out of the box.





The camel-ignite-messaging source connector has no aggregation strategies out of the box.




// kafka-connector options: END
