camel-reactive-streams-kafka-connector source configuration

When using camel-reactive-streams-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-reactive-streams-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.reactivestreams.CamelReactivestreamsSourceConnector

The camel-reactive-streams source connector supports 18 options, which are listed below.

Name	Description	Default	Priority
camel.source.path.stream	Name of the stream channel used by the endpoint to exchange messages.	null	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	MEDIUM
camel.source.endpoint.concurrentConsumers	Number of threads used to process exchanges in the Camel route.	1	MEDIUM
camel.source.endpoint.exchangesRefillLowWatermark	Set the low watermark of requested exchanges to the active subscription as percentage of the maxInflightExchanges. When the number of pending items from the upstream source is lower than the watermark, new items can be requested to the subscription. If set to 0, the subscriber will request items in batches of maxInflightExchanges, only after all items of the previous batch have been processed. If set to 1, the subscriber can request a new item each time an exchange is processed (chatty). Any intermediate value can be used.	0.25D	MEDIUM
camel.source.endpoint.forwardOnComplete	Determines if onComplete events should be pushed to the Camel route.	false	MEDIUM
camel.source.endpoint.forwardOnError	Determines if onError events should be pushed to the Camel route. Exceptions will be set as message body.	false	MEDIUM
camel.source.endpoint.maxInflightExchanges	Maximum number of exchanges concurrently being processed by Camel. This parameter controls backpressure on the stream. Setting a non-positive value will disable backpressure.	"128"	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	MEDIUM
camel.source.endpoint.exchangePattern	Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]	null	MEDIUM
camel.source.endpoint.basicPropertyBinding	Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities	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	MEDIUM
camel.component.reactive-streams.threadPoolMaxSize	The maximum number of threads used by the reactive streams internal engine.	10	MEDIUM
camel.component.reactive-streams.threadPoolMinSize	The minimum number of threads used by the reactive streams internal engine.	null	MEDIUM
camel.component.reactive-streams.threadPoolName	The name of the thread pool used by the reactive streams internal engine.	"CamelReactiveStreamsWorker"	MEDIUM
camel.component.reactive-streams.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	MEDIUM
camel.component.reactive-streams.basicProperty Binding	Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities	false	MEDIUM
camel.component.reactive-streams.reactiveStreams EngineConfiguration	To use an existing reactive stream engine configuration.	null	MEDIUM
camel.component.reactive-streams.serviceType	Set the type of the underlying reactive streams implementation to use. The implementation is looked up from the registry or using a ServiceLoader, the default implementation is DefaultCamelReactiveStreamsService	null	MEDIUM

Name

Description

Default

Priority

camel.source.path.stream

Name of the stream channel used by the endpoint to exchange messages.

null

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

MEDIUM

camel.source.endpoint.concurrentConsumers

Number of threads used to process exchanges in the Camel route.

MEDIUM

camel.source.endpoint.exchangesRefillLowWatermark

Set the low watermark of requested exchanges to the active subscription as percentage of the maxInflightExchanges. When the number of pending items from the upstream source is lower than the watermark, new items can be requested to the subscription. If set to 0, the subscriber will request items in batches of maxInflightExchanges, only after all items of the previous batch have been processed. If set to 1, the subscriber can request a new item each time an exchange is processed (chatty). Any intermediate value can be used.

0.25D

MEDIUM

camel.source.endpoint.forwardOnComplete

Determines if onComplete events should be pushed to the Camel route.

false

MEDIUM

camel.source.endpoint.forwardOnError

Determines if onError events should be pushed to the Camel route. Exceptions will be set as message body.

false

MEDIUM

camel.source.endpoint.maxInflightExchanges

Maximum number of exchanges concurrently being processed by Camel. This parameter controls backpressure on the stream. Setting a non-positive value will disable backpressure.

"128"

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

MEDIUM

camel.source.endpoint.exchangePattern

Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]

null

MEDIUM

camel.source.endpoint.basicPropertyBinding

Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities

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

MEDIUM

camel.component.reactive-streams.threadPoolMaxSize

The maximum number of threads used by the reactive streams internal engine.

MEDIUM

camel.component.reactive-streams.threadPoolMinSize

The minimum number of threads used by the reactive streams internal engine.

null

MEDIUM

camel.component.reactive-streams.threadPoolName

The name of the thread pool used by the reactive streams internal engine.

"CamelReactiveStreamsWorker"

MEDIUM

camel.component.reactive-streams.bridgeError Handler

false

MEDIUM

camel.component.reactive-streams.basicProperty Binding

Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities

false

MEDIUM

camel.component.reactive-streams.reactiveStreams EngineConfiguration

To use an existing reactive stream engine configuration.

null

MEDIUM

camel.component.reactive-streams.serviceType

Set the type of the underlying reactive streams implementation to use. The implementation is looked up from the registry or using a ServiceLoader, the default implementation is DefaultCamelReactiveStreamsService

null

MEDIUM