Server : Apache System : Linux server2.corals.io 4.18.0-348.2.1.el8_5.x86_64 #1 SMP Mon Nov 15 09:17:08 EST 2021 x86_64 User : corals ( 1002) PHP Version : 7.4.33 Disable Function : exec,passthru,shell_exec,system Directory : /home/corals/old/vendor/elasticsearch/elasticsearch/docs/ |
[[search_operations]]
=== Search operations
Well...it isn't called {es} for nothing! Let's talk about search operations in
the client.
The client gives you full access to every query and parameter exposed by the
REST API, following the naming scheme as much as possible. Let's look at a few
examples so you can become familiar with the syntax.
[discrete]
==== Match query
Here is a standard curl for a match query:
[source,shell]
----
curl -XGET 'localhost:9200/my_index/_search' -d '{
"query" : {
"match" : {
"testField" : "abc"
}
}
}'
----
{zwsp} +
And here is the same query constructed in the client:
[source,php]
----
$params = [
'index' => 'my_index',
'body' => [
'query' => [
'match' => [
'testField' => 'abc'
]
]
]
];
$results = $client->search($params);
----
{zwsp} +
Notice how the structure and layout of the PHP array is identical to that of the
JSON request body. This makes it very simple to convert JSON examples into PHP.
A quick method to check your PHP array (for more complex examples) is to encode
it back to JSON and check it:
[source,php]
----
$params = [
'index' => 'my_index',
'body' => [
'query' => [
'match' => [
'testField' => 'abc'
]
]
]
];
print_r(json_encode($params['body']));
{"query":{"match":{"testField":"abc"}}}
----
{zwsp} +
.Using Raw JSON
****
Sometimes it is convenient to use raw JSON for testing purposes, or when
migrating from a different system. You can use raw JSON as a string in the body,
and the client detects this automatically:
[source,php]
----
$json = '{
"query" : {
"match" : {
"testField" : "abc"
}
}
}';
$params = [
'index' => 'my_index',
'body' => $json
];
$results = $client->search($params);
----
****
{zwsp} +
Search results follow the same format as {es} search response, the only
difference is that the JSON response is serialized back into PHP arrays. Working
with the search results is as simple as iterating over the array values:
[source,php]
----
$params = [
'index' => 'my_index',
'body' => [
'query' => [
'match' => [
'testField' => 'abc'
]
]
]
];
$results = $client->search($params);
$milliseconds = $results['took'];
$maxScore = $results['hits']['max_score'];
$score = $results['hits']['hits'][0]['_score'];
$doc = $results['hits']['hits'][0]['_source'];
----
{zwsp} +
[discrete]
==== Bool Queries
Bool queries can be easily constructed using the client. For example, this
query:
[source,shell]
----
curl -XGET 'localhost:9200/my_index/_search' -d '{
"query" : {
"bool" : {
"must": [
{
"match" : { "testField" : "abc" }
},
{
"match" : { "testField2" : "xyz" }
}
]
}
}
}'
----
{zwsp} +
Would be structured like this (note the position of the square brackets):
[source,php]
----
$params = [
'index' => 'my_index',
'body' => [
'query' => [
'bool' => [
'must' => [
[ 'match' => [ 'testField' => 'abc' ] ],
[ 'match' => [ 'testField2' => 'xyz' ] ],
]
]
]
]
];
$results = $client->search($params);
----
{zwsp} +
Notice that the `must` clause accepts an array of arrays. This is serialized
into an array of JSON objects internally, so the final resulting output is
identical to the curl example. For more details about arrays and objects in PHP,
see <<php_json_objects, Dealing with JSON Arrays and Objects in PHP>>.
[discrete]
==== A more complicated example
Let's construct a slightly more complicated example: a boolean query that
contains both a filter and a query. This is a very common activity in {es}
queries, so it will be a good demonstration.
The curl version of the query:
[source,shell]
----
curl -XGET 'localhost:9200/my_index/_search' -d '{
"query" : {
"bool" : {
"filter" : {
"term" : { "my_field" : "abc" }
},
"should" : {
"match" : { "my_other_field" : "xyz" }
}
}
}
}'
----
{zwsp} +
And in PHP:
[source,php]
----
$params = [
'index' => 'my_index',
'body' => [
'query' => [
'bool' => [
'filter' => [
'term' => [ 'my_field' => 'abc' ]
],
'should' => [
'match' => [ 'my_other_field' => 'xyz' ]
]
]
]
]
];
$results = $client->search($params);
----
{zwsp} +
[discrete]
==== Scrolling
The scrolling functionality of {es} is used to paginate over many documents in a
bulk manner, such as exporting all the documents belonging to a single user. It
is more efficient than regular search because it doesn't need to maintain an
expensive priority queue ordering the documents.
Scrolling works by maintaining a "point in time" snapshot of the index which is
then used to page over. This window allows consistent paging even if there is
background indexing/updating/deleting. First, you execute a search request with
`scroll` enabled. This returns a "page" of documents, and a `scroll_id` which is
used to continue paginating through the hits.
More details about scrolling can be found in the
{ref-7x}/search-request-body.html#request-body-search-scroll[reference documentation].
This is an example which can be used as a template for more advanced operations:
[source,php]
----
$client = ClientBuilder::create()->build();
$params = [
'scroll' => '30s', // how long between scroll requests. should be small!
'size' => 50, // how many results *per shard* you want back
'index' => 'my_index',
'body' => [
'query' => [
'match_all' => new \stdClass()
]
]
];
// Execute the search
// The response will contain the first batch of documents
// and a scroll_id
$response = $client->search($params);
// Now we loop until the scroll "cursors" are exhausted
while (isset($response['hits']['hits']) && count($response['hits']['hits']) > 0) {
// **
// Do your work here, on the $response['hits']['hits'] array
// **
// When done, get the new scroll_id
// You must always refresh your _scroll_id! It can change sometimes
$scroll_id = $response['_scroll_id'];
// Execute a Scroll request and repeat
$response = $client->scroll([
'body' => [
'scroll_id' => $scroll_id, //...using our previously obtained _scroll_id
'scroll' => '30s' // and the same timeout window
]
]);
}
----