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

When using camel-jclouds-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-jclouds-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.jclouds.CamelJcloudsSourceConnector
----


The camel-jclouds 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.command* | What command to execute such as blobstore or compute. One of: [blobstore] [compute] | null | true | HIGH
| *camel.source.path.providerId* | The name of the cloud provider that provides the target service (e.g. aws-s3 or aws_ec2). | null | true | HIGH
| *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.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | false | MEDIUM
| *camel.source.endpoint.container* | The name of the blob container. | null | false | MEDIUM
| *camel.source.endpoint.directory* | An optional directory name to use | null | false | MEDIUM
| *camel.component.jclouds.blobStores* | To use the given BlobStore which must be configured when using blobstore. | null | false | MEDIUM
| *camel.component.jclouds.computeServices* | To use the given ComputeService which must be configured when use compute. | null | false | MEDIUM
| *camel.component.jclouds.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.component.jclouds.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-jclouds source connector has no converters out of the box.





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





The camel-jclouds source connector has no aggregation strategies out of the box.
// kafka-connector options: END
