Etcd Watch
Since Camel 2.18
Only consumer is supported
The camel Etcd component allows you to work with Etcd, a distributed reliable key-value store.
Configuring Options
Camel components are configured on two separate levels:
-
component level
-
endpoint level
Configuring Component Options
The component level is the highest level which holds general and common configurations that are inherited by the endpoints. For example a component may have security settings, credentials for authentication, urls for network connection and so forth.
Some components only have a few options, and others may have many. Because components typically have pre configured defaults that are commonly used, then you may often only need to configure a few options on a component; or none at all.
Configuring components can be done with the Component DSL, in a configuration file (application.properties|yaml), or directly with Java code.
Configuring Endpoint Options
Where you find yourself configuring the most is on endpoints, as endpoints often have many options, which allows you to configure what you need the endpoint to do. The options are also categorized into whether the endpoint is used as consumer (from) or as a producer (to), or used for both.
Configuring endpoints is most often done directly in the endpoint URI as path and query parameters. You can also use the Endpoint DSL as a type safe way of configuring endpoints.
A good practice when configuring options is to use Property Placeholders, which allows to not hardcode urls, port numbers, sensitive information, and other settings. In other words placeholders allows to externalize the configuration from your code, and gives more flexibility and reuse.
The following two sections lists all the options, firstly for the component followed by the endpoint.
Component Options
The Etcd Watch component supports 13 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
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 |
boolean |
|
Component configuration. |
EtcdConfiguration |
||
To apply an action recursively. |
false |
boolean |
|
The path to look for for service discovery. |
/services/ |
String |
|
To set the maximum time an action could take to complete. |
Long |
||
To set the URIs the client connects. |
String |
||
To send an empty message in case of timeout watching for a key. |
false |
boolean |
|
The index to watch from. |
0 |
long |
|
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 |
boolean |
|
The password to use for basic authentication. |
String |
||
To configure security using SSLContextParameters. |
SSLContextParameters |
||
Enable usage of global SSL context parameters. |
false |
boolean |
|
The user name to use for basic authentication. |
String |
Endpoint Options
The Etcd Watch endpoint is configured using URI syntax:
etcd-watch:path
with the following path and query parameters:
Query Parameters (12 parameters)
| Name | Description | Default | Type |
|---|---|---|---|
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 |
boolean |
|
To apply an action recursively. |
false |
boolean |
|
The path to look for for service discovery. |
/services/ |
String |
|
To set the URIs the client connects. |
String |
||
To send an empty message in case of timeout watching for a key. |
false |
boolean |
|
To set the maximum time an action could take to complete. |
Long |
||
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. |
ExceptionHandler |
||
Sets the exchange pattern when the consumer creates an exchange. Enum values:
|
ExchangePattern |
||
The index to watch from. |
0 |
long |
|
The password to use for basic authentication. |
String |
||
To configure security using SSLContextParameters. |
SSLContextParameters |
||
The user name to use for basic authentication. |
String |
Spring Boot Auto-Configuration
When using etcd-watch with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-etcd-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>The component supports 43 options, which are listed below.