camel-zookeeper-master-kafka-connector source configuration

Connector description: Have only a single consumer in a cluster consuming from a given endpoint; with automatic failover if the JVM dies.

When using camel-zookeeper-master-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-zookeeper-master-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.zookeepermaster.CamelZookeepermasterSourceConnector

The camel-zookeeper-master source connector supports 13 options, which are listed below.

Name Description Default Required Priority

camel.source.path.groupName

The name of the cluster group to use

null

true

HIGH

camel.source.path.consumerEndpointUri

The consumer endpoint to use in master/slave mode

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.component.zookeeper-master.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.zookeeper-master.maximumConnection Timeout

Timeout in millis to use when connecting to the zookeeper ensemble

10000

false

MEDIUM

camel.component.zookeeper-master.zkRoot

The root path to use in zookeeper where information is stored which nodes are master/slave etc. Will by default use: /camel/zookeepermaster/clusters/master

"/camel/zookeepermaster/clusters/master"

false

MEDIUM

camel.component.zookeeper-master.zooKeeperUrl

The url for the zookeeper ensemble

"localhost:2181"

false

MEDIUM

camel.component.zookeeper-master.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

camel.component.zookeeper-master.containerId Factory

To use a custom ContainerIdFactory for creating container ids.

null

false

MEDIUM

camel.component.zookeeper-master.curator

To use a custom configured CuratorFramework as connection to zookeeper ensemble.

null

false

MEDIUM

camel.component.zookeeper-master.zooKeeperPassword

The password to use when connecting to the zookeeper ensemble

null

false

MEDIUM

The camel-zookeeper-master source connector has no converters out of the box.

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

The camel-zookeeper-master source connector has no aggregation strategies out of the box.

Back to top