Quickstartedit
This section will give you a quick overview of the client and how the major functions work.
Installationedit
Include elasticsearch-php in your
composer.json
file:{ "require": { "elasticsearch/elasticsearch": "~5.0" } }
Install the client with composer:
curl -s http://getcomposer.org/installer | php php composer.phar install --no-dev
Include the autoloader in your main project (if you haven’t already), and instantiate a new client :
require 'vendor/autoload.php'; $client = ClientBuilder::create()->build();
Index a documentedit
In elasticsearch-php, almost everything is configured by associative arrays. The REST endpoint, document and optional parameters - everything is an associative array.
To index a document, we need to specify four pieces of information: index, type, id and a document body. This is done by constructing an associative array of key:value pairs. The request body is itself an associative array with key:value pairs corresponding to the data in your document:
$params = [ 'index' => 'my_index', 'type' => 'my_type', 'id' => 'my_id', 'body' => ['testField' => 'abc'] ]; $response = $client->index($params); print_r($response);
The response that you get back indicates the document was created in the index that you specified. The response is an associative array containing a decoded version of the JSON that Elasticsearch returns:
Array ( [_index] => my_index [_type] => my_type [_id] => my_id [_version] => 1 [created] => 1 )
Get a documentedit
Let’s get the document that we just indexed. This will simply return the document:
$params = [ 'index' => 'my_index', 'type' => 'my_type', 'id' => 'my_id' ]; $response = $client->get($params); print_r($response);
The response contains some metadata (index, type, etc) as well as a _source
field…this is the original document
that you sent to Elasticsearch.
Array ( [_index] => my_index [_type] => my_type [_id] => my_id [_version] => 1 [found] => 1 [_source] => Array ( [testField] => abc ) )
Search for a documentedit
Searching is a hallmark of elasticsearch, so let’s perform a search. We are going to use the Match query as a demonstration:
$params = [ 'index' => 'my_index', 'type' => 'my_type', 'body' => [ 'query' => [ 'match' => [ 'testField' => 'abc' ] ] ] ]; $response = $client->search($params); print_r($response);
The response is a little different from the previous responses. We see some metadata (took
, timed_out
, etc) and
an array named hits
. This represents your search results. Inside of hits
is another array named hits
, which contains
individual search results:
Array ( [took] => 1 [timed_out] => [_shards] => Array ( [total] => 5 [successful] => 5 [failed] => 0 ) [hits] => Array ( [total] => 1 [max_score] => 0.30685282 [hits] => Array ( [0] => Array ( [_index] => my_index [_type] => my_type [_id] => my_id [_score] => 0.30685282 [_source] => Array ( [testField] => abc ) ) ) ) )
Delete a documentedit
Alright, let’s go ahead and delete the document that we added previously:
$params = [ 'index' => 'my_index', 'type' => 'my_type', 'id' => 'my_id' ]; $response = $client->delete($params); print_r($response);
You’ll notice this is identical syntax to the get
syntax. The only difference is the operation: delete
instead of
get
. The response will confirm the document was deleted:
Array ( [found] => 1 [_index] => my_index [_type] => my_type [_id] => my_id [_version] => 2 )
Delete an indexedit
Due to the dynamic nature of elasticsearch, the first document we added automatically built an index with some default settings. Let’s delete that index because we want to specify our own settings later:
$deleteParams = [ 'index' => 'my_index' ]; $response = $client->indices()->delete($deleteParams); print_r($response);
The response:
Array ( [acknowledged] => 1 )
Create an indexedit
Now that we are starting fresh (no data or index), let’s add a new index with some custom settings:
$params = [ 'index' => 'my_index', 'body' => [ 'settings' => [ 'number_of_shards' => 2, 'number_of_replicas' => 0 ] ] ]; $response = $client->indices()->create($params); print_r($response);
Elasticsearch will now create that index with your chosen settings, and return an acknowledgement:
Array ( [acknowledged] => 1 )
Wrap upedit
That was just a crash-course overview of the client and it’s syntax. If you are familiar with elasticsearch, you’ll notice that the methods are named just like REST endpoints.
You’ll also notice that the client is configured in a manner that facilitates easy discovery via your IDE. All core
actions are available under the $client
object (indexing, searching, getting, etc). Index and cluster management
are located under the $client->indices()
and $client->cluster()
objects, respectively.
Check out the rest of the Documentation to see how the entire client works.