// kafka-connector options: START
[[camel-disruptor-vm-kafka-connector-sink]]
= camel-disruptor-vm-kafka-connector sink configuration

Connector Description: Provides asynchronous SEDA behavior using LMAX Disruptor.

When using camel-disruptor-vm-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-disruptor-vm-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.disruptorvm.CamelDisruptorvmSinkConnector
----


The camel-disruptor-vm sink connector supports 12 options, which are listed below.



[width="100%",cols="2,5,^1,1,1",options="header"]
|===
| Name | Description | Default | Required | Priority
| *camel.sink.path.name* | Name of queue | null | true | HIGH
| *camel.sink.endpoint.size* | The maximum capacity of the Disruptors ringbuffer Will be effectively increased to the nearest power of two. Notice: Mind if you use this option, then its the first endpoint being created with the queue name, that determines the size. To make sure all endpoints use same size, then configure the size option on all of them, or the first endpoint being created. | 1024 | false | MEDIUM
| *camel.sink.endpoint.blockWhenFull* | Whether a thread that sends messages to a full Disruptor will block until the ringbuffer's capacity is no longer exhausted. By default, the calling thread will block and wait until the message can be accepted. By disabling this option, an exception will be thrown stating that the queue is full. | false | 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.producerType* | Defines the producers allowed on the Disruptor. The options allowed are: Multi to allow multiple producers and Single to enable certain optimizations only allowed when one concurrent producer (on one thread or otherwise synchronized) is active. One of: [Single] [Multi] | "Multi" | false | MEDIUM
| *camel.sink.endpoint.timeout* | Timeout (in milliseconds) before a producer will stop waiting for an asynchronous task to complete. You can disable timeout by using 0 or a negative value. | 30000L | false | MEDIUM
| *camel.sink.endpoint.waitForTaskToComplete* | Option to specify whether the caller should wait for the async task to complete or not before continuing. The following three options are supported: Always, Never or IfReplyExpected. The first two values are self-explanatory. The last value, IfReplyExpected, will only wait if the message is Request Reply based. One of: [Never] [IfReplyExpected] [Always] | "IfReplyExpected" | false | MEDIUM
| *camel.component.disruptor-vm.bufferSize* | To configure the ring buffer size | 1024 | false | MEDIUM
| *camel.component.disruptor-vm.defaultBlockWhenFull* | To configure the default value for block when full The default value is true. | true | false | MEDIUM
| *camel.component.disruptor-vm.defaultProducerType* | To configure the default value for DisruptorProducerType The default value is Multi. One of: [Single] [Multi] | "Multi" | false | MEDIUM
| *camel.component.disruptor-vm.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.disruptor-vm.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-disruptor-vm sink connector has no converters out of the box.





The camel-disruptor-vm sink connector has no transforms out of the box.





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