Elasticsearch Low level Rest Client
Since Camel 4.3
Only producer is supported
The ElasticSearch component allows you to interface with ElasticSearch 8.x API or OpenSearch using the ElasticSearch Java Low level Rest Client.
Maven users will need to add the following dependency to their pom.xml
for this component:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-elasticsearch-rest-client</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
Configuring Options
Camel components are configured on two separate levels:
-
component level
-
endpoint level
Configuring Component Options
At the component level, you set general and shared configurations that are, then, inherited by the endpoints. It is the highest configuration level.
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.
You can configure components using:
-
the Component DSL.
-
in a configuration file (
application.properties
,*.yaml
files, etc). -
directly in the Java code.
Configuring Endpoint Options
You usually spend more time setting up endpoints because they have many options. These options help you customize what you want the endpoint to do. The options are also categorized into whether the endpoint is used as a consumer (from), as a producer (to), or both.
Configuring endpoints is most often done directly in the endpoint URI as path and query parameters. You can also use the Endpoint DSL and DataFormat DSL as a type safe way of configuring endpoints and data formats in Java.
A good practice when configuring options is to use Property Placeholders.
Property placeholders provide a few benefits:
-
They help prevent using hardcoded urls, port numbers, sensitive information, and other settings.
-
They allow externalizing the configuration from the code.
-
They help the code to become more flexible and reusable.
The following two sections list all the options, firstly for the component followed by the endpoint.
Component Options
The Elasticsearch Low level Rest Client component supports 12 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
Connection timeout. | 30000 | int | |
List of host Addresses, multiple hosts can be separated by comma. | String | ||
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 | boolean | |
Socket timeout. | 30000 | int | |
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 | |
Enabling Sniffer. | false | boolean | |
Autowired Rest Client of type org.elasticsearch.client.RestClient. This is only for advanced usage. | RestClient | ||
Sniffer after failure delay (in millis). | 60000 | int | |
Sniffer interval (in millis). | 60000 | int | |
Certificate Path. | String | ||
Password. | String | ||
Username. | String |
Endpoint Options
The Elasticsearch Low level Rest Client endpoint is configured using URI syntax:
elasticsearch-rest-client:clusterName
With the following path and query parameters:
Query Parameters (13 parameters)
Name | Description | Default | Type |
---|---|---|---|
Connection timeout. | 30000 | int | |
List of host Addresses, multiple hosts can be separated by comma. | String | ||
Index Name. | String | ||
Required Operation. Enum values:
| ElasticsearchRestClientOperation | ||
Socket timeout. | 30000 | int | |
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 | boolean | |
Enabling Sniffer. | false | boolean | |
Autowired Rest Client of type org.elasticsearch.client.RestClient. This is only for advanced usage. | RestClient | ||
Sniffer after failure delay (in millis). | 60000 | int | |
Sniffer interval (in millis). | 60000 | int | |
Certificate Path. | String | ||
Password. | String | ||
Username. | String |
Message Headers
The Elasticsearch Low level Rest Client component supports 4 message header(s), which is/are listed below:
Name | Description | Default | Type |
---|---|---|---|
Constant: | ID of the object to index or retrieve or delete. | String | |
Constant: | The JSON Query to perform for search. | String | |
Constant: | Advanced - The JSON Index Settings and/or Mappings Query to perform to create an index. | String | |
Constant: | The Index name. | String |
Elasticsearch Low level Rest Client Operations
The following operations are currently supported.
operation | message body | description |
---|---|---|
|
| Adds or updates content to an index and returns the resulting |
|
| Retrieves a JSON String representation of the indexed document, corresponding to the given index id and sets it as the message exchange body. You can set the name of the target index from the |
|
| Deletes the specified |
| Creates the specified | |
| Deletes the specified | |
|
| Search for content with either a |
Examples
Index Content Example
To index some content.
from("direct:index")
.setBody().constant("{\"content\": \"ElasticSearch With Camel\"}")
.to("elasticsearch-rest-client://myCluster?operation=INDEX_OR_UPDATE&indexName=myIndex");
To update existing indexed content, provide the ID
message header and the message body with the updated content.
from("direct:index")
.setHeader("ID").constant("1")
.setBody().constant("{\"content\": \"ElasticSearch REST Client With Camel\"}")
.to("elasticsearch-rest-client://myCluster?operation=INDEX_OR_UPDATE&indexName=myIndex");
Get By ID Example
from("direct:getById")
.setHeader("ID").constant("1")
.to("elasticsearch-rest-client://myCluster?operation=GET_BY_ID&indexName=myIndex");
Delete Example
To delete indexed content, provide the ID
message header.
from("direct:getById")
.setHeader("ID").constant("1")
.to("elasticsearch-rest-client://myCluster?operation=DELETE&indexName=myIndex");
Create Index Example
To create a new index.
from("direct:createIndex")
.to("elasticsearch-rest-client://myCluster?operation=CREATE_INDEX&indexName=myIndex");
To create a new index with some custom settings.
String indexSettings = "{\"settings\":{\"number_of_replicas\": 1,\"number_of_shards\": 3,\"analysis\": {},\"refresh_interval\": \"1s\"},\"mappings\":{\"dynamic\": false,\"properties\": {\"title\": {\"type\": \"text\", \"analyzer\": \"english\"}}}}";
from("direct:createIndex")
.setHeader("INDEX_SETTINGS").constant(indexSettings)
.to("elasticsearch-rest-client://myCluster?operation=CREATE_INDEX&indexName=myIndex");
Delete Index Example
To delete an index.
from("direct:deleteIndex")
.to("elasticsearch-rest-client://myCluster?operation=DELETE_INDEX&indexName=myIndex");
Search Example
Search with a JSON query.
from("direct:search")
.setHeader("SEARCH_QUERY").constant("{\"query\":{\"match\":{\"content\":\"ElasticSearch With Camel\"}}}")
.to("elasticsearch-rest-client://myCluster?operation=SEARCH&indexName=myIndex");
Search on specific field(s) using Map
.
Map<String, String> criteria = new HashMap<>();
criteria.put("content", "Camel");
from("direct:search")
.setBody().constant(criteria)
.to("elasticsearch-rest-client://myCluster?operation=SEARCH&indexName=myIndex");
Spring Boot Auto-Configuration
When using elasticsearch-rest-client 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-elasticsearch-rest-client-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
The component supports 13 options, which are listed below.