// kafka-connector options: START
[[camel-twitter-directmessage-kafka-connector-sink]]
= camel-twitter-directmessage-kafka-connector sink configuration

When using camel-twitter-directmessage-kafka-connector as sink 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-twitter-directmessage-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

[source,java]
----
connector.class=org.apache.camel.kafkaconnector.twitterdirectmessage.CamelTwitterdirectmessageSinkConnector
----


The camel-twitter-directmessage sink connector supports 21 options, which are listed below.



[width="100%",cols="2,5,^1,1,1",options="header"]
|===
| Name | Description | Default | Required | Priority
| *camel.sink.path.user* | The user name to send a direct message. This will be ignored for consumer. | null | true | HIGH
| *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.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | false | MEDIUM
| *camel.sink.endpoint.httpProxyHost* | The http proxy host which can be used for the camel-twitter. Can also be configured on the TwitterComponent level instead. | null | false | MEDIUM
| *camel.sink.endpoint.httpProxyPassword* | The http proxy password which can be used for the camel-twitter. Can also be configured on the TwitterComponent level instead. | null | false | MEDIUM
| *camel.sink.endpoint.httpProxyPort* | The http proxy port which can be used for the camel-twitter. Can also be configured on the TwitterComponent level instead. | null | false | MEDIUM
| *camel.sink.endpoint.httpProxyUser* | The http proxy user which can be used for the camel-twitter. Can also be configured on the TwitterComponent level instead. | null | false | MEDIUM
| *camel.sink.endpoint.accessToken* | The access token. Can also be configured on the TwitterComponent level instead. | null | false | MEDIUM
| *camel.sink.endpoint.accessTokenSecret* | The access secret. Can also be configured on the TwitterComponent level instead. | null | false | MEDIUM
| *camel.sink.endpoint.consumerKey* | The consumer key. Can also be configured on the TwitterComponent level instead. | null | false | MEDIUM
| *camel.sink.endpoint.consumerSecret* | The consumer secret. Can also be configured on the TwitterComponent level instead. | null | false | MEDIUM
| *camel.component.twitter-directmessage.lazyStart Producer* | 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.twitter-directmessage.autowired Enabled* | 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
| *camel.component.twitter-directmessage.httpProxy Host* | The http proxy host which can be used for the camel-twitter. | null | false | MEDIUM
| *camel.component.twitter-directmessage.httpProxy Password* | The http proxy password which can be used for the camel-twitter. | null | false | MEDIUM
| *camel.component.twitter-directmessage.httpProxy Port* | The http proxy port which can be used for the camel-twitter. | null | false | MEDIUM
| *camel.component.twitter-directmessage.httpProxy User* | The http proxy user which can be used for the camel-twitter. | null | false | MEDIUM
| *camel.component.twitter-directmessage.accessToken* | The access token | null | false | MEDIUM
| *camel.component.twitter-directmessage.accessToken Secret* | The access token secret | null | false | MEDIUM
| *camel.component.twitter-directmessage.consumerKey* | The consumer key | null | false | MEDIUM
| *camel.component.twitter-directmessage.consumer Secret* | The consumer secret | null | false | MEDIUM
|===



The camel-twitter-directmessage sink connector has no converters out of the box.





The camel-twitter-directmessage sink connector has no transforms out of the box.





The camel-twitter-directmessage sink connector has no aggregation strategies out of the box.
// kafka-connector options: END
