camel-zookeeper-kafka-connector sink configuration
When using camel-zookeeper-kafka-connector as sink make sure to use the following Maven dependency to have support for the connector:
<dependency>
<groupId>org.apache.camel.kafkaconnector</groupId>
<artifactId>camel-zookeeper-kafka-connector</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel Kafka connector version -->
</dependency>The camel-zookeeper sink connector supports 16 options, which are listed below.
| Name | Description | Default | Priority |
|---|---|---|---|
camel.sink.path.serverUrls |
The zookeeper server hosts (multiple servers can be separated by comma) |
null |
HIGH |
camel.sink.path.path |
The node in the ZooKeeper server (aka znode) |
null |
HIGH |
camel.sink.endpoint.listChildren |
Whether the children of the node should be listed |
false |
MEDIUM |
camel.sink.endpoint.timeout |
The time interval to wait on connection before timing out. |
5000 |
MEDIUM |
camel.sink.endpoint.create |
Should the endpoint create the node if it does not currently exist. |
false |
MEDIUM |
camel.sink.endpoint.createMode |
The create mode that should be used for the newly created node One of: [PERSISTENT] [PERSISTENT_SEQUENTIAL] [EPHEMERAL] [EPHEMERAL_SEQUENTIAL] |
"EPHEMERAL" |
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 |
MEDIUM |
camel.sink.endpoint.basicPropertyBinding |
Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
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 |
MEDIUM |
camel.component.zookeeper.listChildren |
Whether the children of the node should be listed |
false |
MEDIUM |
camel.component.zookeeper.timeout |
The time interval to wait on connection before timing out. |
5000 |
MEDIUM |
camel.component.zookeeper.create |
Should the endpoint create the node if it does not currently exist. |
false |
MEDIUM |
camel.component.zookeeper.createMode |
The create mode that should be used for the newly created node One of: [PERSISTENT] [PERSISTENT_SEQUENTIAL] [EPHEMERAL] [EPHEMERAL_SEQUENTIAL] |
"EPHEMERAL" |
MEDIUM |
camel.component.zookeeper.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 |
MEDIUM |
camel.component.zookeeper.basicPropertyBinding |
Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
MEDIUM |
camel.component.zookeeper.configuration |
To use a shared ZooKeeperConfiguration |
null |
MEDIUM |