Table of Content - Elasticsearch Curl Commands with Examples |
We use HTTP requests to talk to ElasticSearch. An HTTP request is made up of several components such as the URL to make the request to, HTTP verbs (GET, POST etc) and headers. In order to succinctly and consistently describe HTTP requests the ElasticSearch documentation uses cURL command line syntax. This is also the standard practice to describe requests made to ElasticSearch within the user community.
An example HTTP request using CURL syntax looks like this:
A simple search request using CURL.
curl -XPOST "https://localhost:9200/_search" -d'
{
"query": {
"match_all": {}
}
}'
The above snippet, when executed in a console, runs the curl program with three arguments. The first argument, -XPOST, means that the request that cURL makes should use the POST HTTP verb. The second argument, is the URL that the request should be made to. The final argument, -d'{…}’
uses the -d flag which instructs cURL to send what follows the flag as the HTTP POST data.
Whenever you see a request formatted using cURL syntax, you can either:
Learn how to use Elasticsearch, from beginner basics to advanced techniques, with online video tutorials taught by industry experts. Enroll for Free Demo at Elasticsearch Training |
When using the last option, pasting cURL formatted requests into Sense, Sense will recognize the cURL syntax and automatically transform it to a request formatted the Sense way. Sense also offers functionality for doing the opposite. When you have a request in Sense, you can click the wrench icon to bring up a dialog offering an option to “Copy as cURL”.
The Copy as CURL dialog in Sense.
For now, just run the below HTTP requests in Sense and take them at face value.
First, let’s index a simple document:
Indexing a simple document using cURL.
curl -XPOST "HTTP://LOCALHOST:9200/MY-FIRST-INDEX/MESSAGE" -d'
{
"text": "Hello world!"
}'
Now, let’s see if we can find it by searching for “hello”:
curl -XPOST "https://localhost:9200/_search" -d'
{
"query": {
"query_string": {
"query": "hello"
}
}
}'
The response from ElasticSearch to the second HTTP request should look like the one below, containing a single hit.
{
"took": 12,
"timed_out": false,
"_shards": {
"total": 12,
"successful": 12,
"failed": 0
},
"hits": {
"total": 1,
"max_score": 0.19178301,
"hits": [
{
"_index": "my-first-index",
"_type": "message",
"_id": "AUqiBnvdK4Rpq0ZV4-Wp",
"_score": 0.19178301,
"_source": {
"text": "Hello world!"
}
}
]
}
}
Curl syntax is programming language agnostic making it perfect to show HTTP interactions in a way that is both succinct and independent of any programming language. However, in the real world, except when debugging, we usually interact with ElasticSearch from our programming language of choice. Let’s look at a couple of examples of how the above requests could be implemented in actual applications.
Related Article: CRUD Operations And Sorting Documents – Elasticsearch |
Elasticsearch Node.js client is official client for Node.js.
For Node.JS, we use the official JavaScript client which can be installed in a Node.JS application using npm install Elasticsearch. A simple application that indexes a single document and then proceeds to search for it, printing the search results to the console, looks like this:
var elasticsearch = require('elasticsearch');
var client = new elasticsearch.Client({
host: 'localhost:9200'
});
//An object that we'll index
var theMessage = {
text: "Hello world!"
};
//Indexing the above object
client.index({
index: "my-first-index",
type: "message",
body: theMessage
}).then(function() {
setTimeout(search, 1100);
});
//Searching and printing the results
function search() {
client.search({
index: "my-first-index",
type: "message",
body: {
query: {
query_string: {
query: "hello"
}
}
}
}).then(function(response) {
console.log("Number of hits: "
+ response.hits.total);
response.hits.hits.forEach(function(hit) {
console.log(hit._source.text);
})
});
}
Note that we add a waiting period between indexing and searching. We do this because an indexed document won’t immediately be searchable after indexing. We have to wait for the index to be refreshed which by default happens every second. It’s possible to require ElasticSearch to immediately refresh the index when indexing a document but that’s bad performance wise and therefore we opt to wait a little.
CheckOut: "Elasticsearch Interview Questions & Answers" |
In the Node.JS example, we (naturally) used JavaScript and the official ElasticSearch client which more or less maps directly to ElasticSearch’s HTTP/JSON API. Therefore, the code for our Node.JS application looked quite similar to the original cURL based example. Now, let’s look how we can interact with ElasticSearch from a strongly typed language, C#, using a client library that introduces more abstractions, NEST.
In order to implement the Hello World example in C#, we start by creating a new console application to which we add the NEST ElasticSearch client using NuGet (PM > Install-Package NEST). Next, we create a class which we’ll index and search for instances of.
A C# class representing a message.
namespace HelloElasticSearch
{
public class Message
{
public Message(string text)
{
Text = text;
}
public string Text { get; private set; }
}
}
The entry point of our application which implements the Hello World example by indexing a message and then searching for it looks like this:
Basic example of indexing and searching using C# and the NEST client library.
using System;
using System.Threading;
using Nest;
namespace HelloElasticSearch
{
class Program
{
static void Main(string[] args)
{
//Create a client that will talk to our ES cluster
var node = new Uri("https://localhost:9200");
var settings = new ConnectionSettings(
node,
defaultIndex: "my-first-index"
);
var client = new ElasticClient(settings);
//Creating and indexing a message object
var theMessage = new Message("Hello world!");
client.Index(theMessage);
//Waiting for the index to be refreshed
Thread.Sleep(1100);
//Search for messages and print the results
var response = client.Search(
body => body.Query(
q => q.QueryString(
qs => qs.Query("hello"))));
Console.WriteLine("Number of hits: " + response.Total);
foreach (var hit in response.Hits)
{
Console.WriteLine(hit.Source.Text);
}
}
}
}
Explore Elasticsearch Sample Resumes! Download & Edit, Get Noticed by Top Employers! |
Our work-support plans provide precise options as per your project tasks. Whether you are a newbie or an experienced professional seeking assistance in completing project tasks, we are here with the following plans to meet your custom needs:
Name | Dates | |
---|---|---|
Elasticsearch Training | Nov 19 to Dec 04 | View Details |
Elasticsearch Training | Nov 23 to Dec 08 | View Details |
Elasticsearch Training | Nov 26 to Dec 11 | View Details |
Elasticsearch Training | Nov 30 to Dec 15 | View Details |
Ravindra Savaram is a Technical Lead at Mindmajix.com. His passion lies in writing articles on the most popular IT platforms including Machine learning, DevOps, Data Science, Artificial Intelligence, RPA, Deep Learning, and so on. You can stay up to date on all these technologies by following him on LinkedIn and Twitter.