honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-17 02:14:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

[Docs] Convert more doc snippets (#26404)

Browse Source 
This commit converts some remaining doc snippets so that they are now
testable.
This commit is contained in:
Tanguy Leroux 2017-08-30 09:30:36 +02:00 committed by GitHub
parent c075323522
commit db54c4dc7c
10 changed files with 264 additions and 173 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/build.gradle
View File

@ -32,15 +32,6 @@ buildRestTests.expectedUnconvertedCandidates = [
'reference/aggregations/matrix/stats-aggregation.asciidoc', 'reference/aggregations/matrix/stats-aggregation.asciidoc',
'reference/aggregations/metrics/tophits-aggregation.asciidoc', 'reference/aggregations/metrics/tophits-aggregation.asciidoc',
'reference/cluster/allocation-explain.asciidoc', 'reference/cluster/allocation-explain.asciidoc',
'reference/cluster/pending.asciidoc',
'reference/cluster/tasks.asciidoc',
'reference/docs/delete-by-query.asciidoc',
'reference/docs/reindex.asciidoc',
'reference/docs/update-by-query.asciidoc',
'reference/index-modules/similarity.asciidoc',
'reference/index-modules/store.asciidoc',
'reference/index-modules/translog.asciidoc',
'reference/search/profile.asciidoc',
] ]
integTestCluster { integTestCluster {

5
docs/reference/cluster/pending.asciidoc
View File

@ -12,8 +12,9 @@ might be reported by both task api and pending cluster tasks API.
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
$ curl -XGET 'http://localhost:9200/_cluster/pending_tasks' GET /_cluster/pending_tasks
-------------------------------------------------- --------------------------------------------------
// CONSOLE
Usually this will return an empty list as cluster-level changes are usually Usually this will return an empty list as cluster-level changes are usually
fast. However if there are tasks queued up, the output will look something fast. However if there are tasks queued up, the output will look something
@ -47,3 +48,5 @@ like this:
] ]
} }
-------------------------------------------------- --------------------------------------------------
// NOTCONSOLE
// We can't test tasks output

5
docs/reference/cluster/tasks.asciidoc
View File

@ -57,6 +57,8 @@ The result will look similar to the following:
} }
} }
-------------------------------------------------- --------------------------------------------------
// NOTCONSOLE
// We can't test tasks output
It is also possible to retrieve information for a particular task: It is also possible to retrieve information for a particular task:
@ -117,6 +119,8 @@ might look like:
} }
} }
-------------------------------------------------- --------------------------------------------------
// NOTCONSOLE
// We can't test tasks output
The new `description` field contains human readable text that identifies the The new `description` field contains human readable text that identifies the
particular request that the task is performing such as identifying the search particular request that the task is performing such as identifying the search
@ -180,7 +184,6 @@ POST _tasks/_cancel?nodes=nodeId1,nodeId2&actions=*reindex
-------------------------------------------------- --------------------------------------------------
// CONSOLE // CONSOLE
[float] [float]
=== Task Grouping === Task Grouping

37
docs/reference/docs/delete-by-query.asciidoc
View File

@ -187,20 +187,47 @@ starting the next set. This is "bursty" instead of "smooth". The default is `-1`
[float] [float]
=== Response body === Response body
//////////////////////////
[source,js]
--------------------------------------------------
POST /twitter/_delete_by_query
{
"query": { <1>
"match": {
"message": "some message"
}
}
}
--------------------------------------------------
// CONSOLE
// TEST[setup:big_twitter]
//////////////////////////
The JSON response looks like this: The JSON response looks like this:
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
{ {
"took" : 639, "took" : 147,
"deleted": 0, "timed_out": false,
"deleted": 119,
"batches": 1, "batches": 1,
"version_conflicts": 2, "version_conflicts": 0,
"retries": 0, "noops": 0,
"retries": {
"bulk": 0,
"search": 0
},
"throttled_millis": 0, "throttled_millis": 0,
"requests_per_second": -1.0,
"throttled_until_millis": 0,
"total": 119,
"failures" : [ ] "failures" : [ ]
} }
-------------------------------------------------- --------------------------------------------------
// TESTRESPONSE[s/: [0-9]+/: $body.$_path/]
`took`:: `took`::
@ -285,6 +312,8 @@ The responses looks like:
} }
} }
-------------------------------------------------- --------------------------------------------------
// NOTCONSOLE
// We can't test tasks output
<1> this object contains the actual status. It is just like the response json <1> this object contains the actual status. It is just like the response json
with the important addition of the `total` field. `total` is the total number with the important addition of the `total` field. `total` is the total number

33
docs/reference/docs/reindex.asciidoc
View File

@ -558,24 +558,49 @@ starting the next set. This is "bursty" instead of "smooth". The default is `-1`
[[docs-reindex-response-body]] [[docs-reindex-response-body]]
=== Response body === Response body
//////////////////////////
[source,js]
--------------------------------------------------
POST /_reindex?wait_for_completion
{
"source": {
"index": "twitter"
},
"dest": {
"index": "new_twitter"
}
}
--------------------------------------------------
// CONSOLE
// TEST[setup:twitter]
//////////////////////////
The JSON response looks like this: The JSON response looks like this:
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
{ {
"took" : 639, "took": 639,
"timed_out": false,
"total": 5,
"updated": 0, "updated": 0,
"created": 123, "created": 123,
"deleted": 0,
"batches": 1, "batches": 1,
"noops": 0,
"version_conflicts": 2, "version_conflicts": 2,
"retries": { "retries": {
"bulk": 0, "bulk": 0,
"search": 0 "search": 0
} },
"throttled_millis": 0, "throttled_millis": 0,
"failures" : [ ] "requests_per_second": 1,
"throttled_until_millis": 0,
"failures": [ ]
} }
-------------------------------------------------- --------------------------------------------------
// TESTRESPONSE[s/: [0-9]+/: $body.$_path/]
`took`:: `took`::
@ -667,6 +692,8 @@ The responses looks like:
} }
} }
-------------------------------------------------- --------------------------------------------------
// NOTCONSOLE
// We can't test tasks output
<1> this object contains the actual status. It is just like the response json <1> this object contains the actual status. It is just like the response json
with the important addition of the `total` field. `total` is the total number with the important addition of the `total` field. `total` is the total number

27
docs/reference/docs/update-by-query.asciidoc
View File

@ -245,23 +245,40 @@ starting the next set. This is "bursty" instead of "smooth". The default is `-1`
[[docs-update-by-query-response-body]] [[docs-update-by-query-response-body]]
=== Response body === Response body
//////////////////////////
[source,js]
--------------------------------------------------
POST /twitter/_update_by_query?conflicts=proceed
--------------------------------------------------
// CONSOLE
// TEST[setup:twitter]
//////////////////////////
The JSON response looks like this: The JSON response looks like this:
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
{ {
"took" : 639, "took" : 147,
"updated": 0, "timed_out": false,
"updated": 5,
"deleted": 0,
"batches": 1, "batches": 1,
"version_conflicts": 2, "version_conflicts": 0,
"noops": 0,
"retries": { "retries": {
"bulk": 0, "bulk": 0,
"search": 0 "search": 0
} },
"throttled_millis": 0, "throttled_millis": 0,
"requests_per_second": -1.0,
"throttled_until_millis": 0,
"total": 5,
"failures" : [ ] "failures" : [ ]
} }
-------------------------------------------------- --------------------------------------------------
// TESTRESPONSE[s/"took" : 147/"took" : "$body.took"/]
`took`:: `took`::
@ -350,6 +367,8 @@ The responses looks like:
} }
} }
-------------------------------------------------- --------------------------------------------------
// NOTCONSOLE
// We can't test tasks output
<1> this object contains the actual status. It is just like the response json <1> this object contains the actual status. It is just like the response json
with the important addition of the `total` field. `total` is the total number with the important addition of the `total` field. `total` is the total number

79
docs/reference/index-modules/similarity.asciidoc
View File

@ -20,29 +20,39 @@ settings.
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
"similarity" : { PUT /index
"my_similarity" : { {
"type" : "DFR", "settings" : {
"basic_model" : "g", "index" : {
"after_effect" : "l", "similarity" : {
"normalization" : "h2", "my_similarity" : {
"normalization.h2.c" : "3.0" "type" : "DFR",
} "basic_model" : "g",
"after_effect" : "l",
"normalization" : "h2",
"normalization.h2.c" : "3.0"
}
}
}
}
} }
-------------------------------------------------- --------------------------------------------------
// CONSOLE
Here we configure the DFRSimilarity so it can be referenced as Here we configure the DFRSimilarity so it can be referenced as
`my_similarity` in mappings as is illustrate in the below example: `my_similarity` in mappings as is illustrate in the below example:
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
PUT /index/_mapping/book
{ {
"book" : { "properties" : {
"properties" : { "title" : { "type" : "text", "similarity" : "my_similarity" }
"title" : { "type" : "text", "similarity" : "my_similarity" } }
}
} }
-------------------------------------------------- --------------------------------------------------
// CONSOLE
// TEST[continued]
[float] [float]
=== Available similarities === Available similarities
@ -173,7 +183,7 @@ TF-IDF:
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
PUT index PUT /index
{ {
"settings": { "settings": {
"number_of_shards": 1, "number_of_shards": 1,
@ -198,19 +208,19 @@ PUT index
} }
} }
PUT index/doc/1 PUT /index/doc/1
{ {
"field": "foo bar foo" "field": "foo bar foo"
} }
PUT index/doc/2 PUT /index/doc/2
{ {
"field": "bar baz" "field": "bar baz"
} }
POST index/_refresh POST /index/_refresh
GET index/_search?explain=true GET /index/_search?explain=true
{ {
"query": { "query": {
"query_string": { "query_string": {
@ -328,7 +338,7 @@ more efficient:
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
PUT index PUT /index
{ {
"settings": { "settings": {
"number_of_shards": 1, "number_of_shards": 1,
@ -362,19 +372,19 @@ PUT index
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
PUT index/doc/1 PUT /index/doc/1
{ {
"field": "foo bar foo" "field": "foo bar foo"
} }
PUT index/doc/2 PUT /index/doc/2
{ {
"field": "bar baz" "field": "bar baz"
} }
POST index/_refresh POST /index/_refresh
GET index/_search?explain=true GET /index/_search?explain=true
{ {
"query": { "query": {
"query_string": { "query_string": {
@ -494,36 +504,41 @@ it is <<indices-create-index,created>>:
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
PUT /my_index PUT /index
{ {
"settings": { "settings": {
"index": { "index": {
"similarity": { "similarity": {
"default": { "default": {
"type": "boolean" "type": "classic"
} }
} }
} }
} }
} }
-------------------------------------------------- --------------------------------------------------
// CONSOLE
If you want to change the default similarity after creating the index If you want to change the default similarity after creating the index
you must <<indices-open-close,close>> your index, send the follwing you must <<indices-open-close,close>> your index, send the following
request and <<indices-open-close,open>> it again afterwards: request and <<indices-open-close,open>> it again afterwards:
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
PUT /my_index/_settings POST /index/_close
PUT /index/_settings
{ {
"settings": { "index": {
"index": { "similarity": {
"similarity": { "default": {
"default": { "type": "classic"
"type": "boolean"
}
} }
} }
} }
} }
POST /index/_open
-------------------------------------------------- --------------------------------------------------
// CONSOLE
// TEST[continued]

2
docs/reference/index-modules/store.asciidoc
View File

@ -31,6 +31,7 @@ PUT /my_index
} }
} }
--------------------------------- ---------------------------------
// CONSOLE
WARNING: This is an expert-only setting and may be removed in the future. WARNING: This is an expert-only setting and may be removed in the future.
@ -108,6 +109,7 @@ PUT /my_index
} }
} }
--------------------------------- ---------------------------------
// CONSOLE
The default value is the empty array, which means that nothing will be loaded The default value is the empty array, which means that nothing will be loaded
into the file-system cache eagerly. For indices that are actively searched, into the file-system cache eagerly. For indices that are actively searched,

2
docs/reference/index-modules/translog.asciidoc
View File

@ -105,7 +105,7 @@ In order to run the `elasticsearch-translog` tool, specify the `truncate`
subcommand as well as the directory for the corrupted translog with the `-d` subcommand as well as the directory for the corrupted translog with the `-d`
option: option:
[source,js] [source,txt]
-------------------------------------------------- --------------------------------------------------
$ bin/elasticsearch-translog truncate -d /var/lib/elasticsearchdata/nodes/0/indices/P45vf_YQRhqjfwLMUvSqDw/0/translog/ $ bin/elasticsearch-translog truncate -d /var/lib/elasticsearchdata/nodes/0/indices/P45vf_YQRhqjfwLMUvSqDw/0/translog/
Checking existing translog files Checking existing translog files

238
docs/reference/search/profile.asciidoc
View File

@ -469,6 +469,17 @@ value is cumulative and contains the total time for all queries being rewritten.
==== A more complex example ==== A more complex example
//////////////////////////
[source,js]
--------------------------------------------------
PUT test
{"settings": {"index.number_of_shards": 1, "number_of_replicas": 0}}
-------------------------------------------------
// CONSOLE
//////////////////////////
To demonstrate a slightly more complex query and the associated results, we can profile the following query: To demonstrate a slightly more complex query and the associated results, we can profile the following query:
[source,js] [source,js]
@ -484,29 +495,17 @@ GET /test/_search
} }
}, },
"aggs": { "aggs": {
"non_global_term": { "my_scoped_agg": {
"terms": { "terms": {
"field": "agg" "field": "level"
},
"aggs": {
"second_term": {
"terms": {
"field": "sub_agg"
}
}
} }
}, },
"another_agg": { "my_global_agg": {
"cardinality": {
"field": "aggB"
}
},
"global_agg": {
"global": {}, "global": {},
"aggs": { "aggs": {
"my_agg2": { "my_level_agg": {
"terms": { "terms": {
"field": "globalAgg" "field": "level"
} }
} }
} }
@ -514,13 +513,14 @@ GET /test/_search
}, },
"post_filter": { "post_filter": {
"term": { "term": {
"my_field": "foo" "tag": "elastic"
} }
} }
} }
-------------------------------------------------- --------------------------------------------------
// CONSOLE // CONSOLE
// TEST[s/^/PUT test\n/] // TEST[s/GET \/test\/_search/GET \/test\/_search\?filter_path=profile.shards.id,profile.shards.searches/]
// TEST[continued]
This example has: This example has:
@ -531,10 +531,10 @@ This example has:
And the response: And the response:
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
{ {
...
"profile": { "profile": {
"shards": [ "shards": [
{ {
@ -548,15 +548,15 @@ And the response:
"time_in_nanos": "409456", "time_in_nanos": "409456",
"breakdown": { "breakdown": {
"score": 0, "score": 0,
"score_count": 1, "build_scorer_count": 1,
"next_doc": 0,
"next_doc_count": 2,
"match": 0,
"match_count": 0, "match_count": 0,
"create_weight": 31584, "create_weight": 31584,
"next_doc": 0,
"match": 0,
"create_weight_count": 1, "create_weight_count": 1,
"next_doc_count": 2,
"score_count": 1,
"build_scorer": 377872, "build_scorer": 377872,
"build_scorer_count": 1,
"advance": 0, "advance": 0,
"advance_count": 0 "advance_count": 0
} }
@ -567,15 +567,15 @@ And the response:
"time_in_nanos": "303702", "time_in_nanos": "303702",
"breakdown": { "breakdown": {
"score": 0, "score": 0,
"score_count": 1, "build_scorer_count": 1,
"next_doc": 5936,
"next_doc_count": 2,
"match": 0,
"match_count": 0, "match_count": 0,
"create_weight": 185215, "create_weight": 185215,
"next_doc": 5936,
"match": 0,
"create_weight_count": 1, "create_weight_count": 1,
"next_doc_count": 2,
"score_count": 1,
"build_scorer": 112551, "build_scorer": 112551,
"build_scorer_count": 1,
"advance": 0, "advance": 0,
"advance_count": 0 "advance_count": 0
} }
@ -584,59 +584,35 @@ And the response:
"rewrite_time": 7208, "rewrite_time": 7208,
"collector": [ "collector": [
{ {
"name": "MultiCollector", "name": "CancellableCollector",
"reason": "search_multi", "reason": "search_cancelled",
"time_in_nanos": "1378943", "time_in_nanos": 2390,
"children": [ "children": [
{ {
"name": "FilteredCollector", "name": "MultiCollector",
"reason": "search_post_filter", "reason": "search_multi",
"time_in_nanos": "403659", "time_in_nanos": 1820,
"children": [ "children": [
{
"name": "FilteredCollector",
"reason": "search_post_filter",
"time_in_nanos": 7735,
"children": [
{ {
"name": "SimpleTopScoreDocCollector", "name": "SimpleTopScoreDocCollector",
"reason": "search_top_hits", "reason": "search_top_hits",
"time_in_nanos": "6391" "time_in_nanos": 1328
} }
] ]
}, },
{ {
"name": "BucketCollector: [[non_global_term, another_agg]]", "name": "BucketCollector: [[org.elasticsearch.search.profile.aggregation.ProfilingAggregator@222b076, org.elasticsearch.search.profile.aggregation.ProfilingAggregator@3000ab31]]",
"reason": "aggregation", "reason": "aggregation",
"time_in_nanos": "954602" "time_in_nanos": 8273
} }
] ]
} }
] ]
},
{
"query": [
{
"type": "MatchAllDocsQuery",
"description": "*:*",
"time_in_nanos": "48293",
"breakdown": {
"score": 0,
"score_count": 1,
"next_doc": 3672,
"next_doc_count": 2,
"match": 0,
"match_count": 0,
"create_weight": 6311,
"create_weight_count": 1,
"build_scorer": 38310,
"build_scorer_count": 1,
"advance": 0,
"advance_count": 0
}
}
],
"rewrite_time": 1067,
"collector": [
{
"name": "GlobalAggregator: [global_agg]",
"reason": "aggregation_global",
"time_in_nanos": "122631"
} }
] ]
} }
@ -646,18 +622,19 @@ And the response:
} }
} }
-------------------------------------------------- --------------------------------------------------
// TESTRESPONSE[s/\.\.\.//]
// TESTRESPONSE[s/: (\-)?[0-9]+/: $body.$_path/]
// TESTRESPONSE[s/: "[^"]*"/: $body.$_path/]
As you can see, the output is significantly verbose from before. All the major portions of the query are As you can see, the output is significantly verbose from before. All the major portions of the query are
represented: represented:
1. The first `TermQuery` (message:search) represents the main `term` query 1. The first `TermQuery` (message:search) represents the main `term` query
2. The second `TermQuery` (my_field:foo) represents the `post_filter` query 2. The second `TermQuery` (my_field:foo) represents the `post_filter` query
3. There is a `MatchAllDocsQuery` (\*:*) query which is being executed as a second, distinct search. This was
not part of the query specified by the user, but is auto-generated by the global aggregation to provide a global query scope
The Collector tree is fairly straightforward, showing how a single MultiCollector wraps a FilteredCollector The Collector tree is fairly straightforward, showing how a single CancellableCollector wraps a MultiCollector
to execute the post_filter (and in turn wraps the normal scoring SimpleCollector), a BucketCollector to run which also wraps a FilteredCollector to execute the post_filter (and in turn wraps the normal scoring SimpleCollector),
all scoped aggregations. In the MatchAll search, there is a single GlobalAggregator to run the global aggregation. a BucketCollector to run all scoped aggregations.
==== Understanding MultiTermQuery output ==== Understanding MultiTermQuery output
@ -682,6 +659,17 @@ Hopefully this will be fixed in future iterations, but it is a tricky problem to
==== `aggregations` Section ==== `aggregations` Section
//////////////////////////
[source,js]
--------------------------------------------------
PUT house-prices
{"settings": {"index.number_of_shards": 1, "number_of_replicas": 0}}
-------------------------------------------------
// CONSOLE
//////////////////////////
The `aggregations` section contains detailed timing of the aggregation tree executed by a particular shard. The `aggregations` section contains detailed timing of the aggregation tree executed by a particular shard.
The overall structure of this aggregation tree will resemble your original Elasticsearch request. Let's consider The overall structure of this aggregation tree will resemble your original Elasticsearch request. Let's consider
the following example aggregations request: the following example aggregations request:
@ -709,47 +697,59 @@ GET /house-prices/_search
} }
-------------------------------------------------- --------------------------------------------------
// CONSOLE // CONSOLE
// TEST[s/^/PUT house-prices\n/] // TEST[s/GET \/house-prices\/_search/GET \/house-prices\/_search\?filter_path=profile.shards.aggregations/]
// TEST[continued]
Which yields the following aggregation profile output Which yields the following aggregation profile output
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
"aggregations": [ {
{ "profile": {
"type": "org.elasticsearch.search.aggregations.bucket.terms.GlobalOrdinalsStringTermsAggregator", "shards": [
"description": "property_type",
"time_in_nanos": "4280456978",
"breakdown": {
"reduce": 0,
"reduce_count": 0,
"build_aggregation": 49765,
"build_aggregation_count": 300,
"initialise": 52785,
"initialize_count": 300,
"collect": 3155490036,
"collect_count": 1800
},
"children": [
{ {
"type": "org.elasticsearch.search.aggregations.metrics.avg.AvgAggregator", ...
"description": "avg_price", "aggregations": [
"time_in_nanos": "1124864392", {
"breakdown": { "type": "org.elasticsearch.search.aggregations.bucket.terms.TermsAggregatorFactory$1",
"reduce": 0, "description": "property_type",
"reduce_count": 0, "time_in_nanos": 26234,
"build_aggregation": 1394, "breakdown": {
"build_aggregation_count": 150, "reduce": 0,
"initialise": 2883, "build_aggregation": 817,
"initialize_count": 150, "build_aggregation_count": 1,
"collect": 1124860115, "initialize": 25415,
"collect_count": 900 "initialize_count": 1,
} "reduce_count": 0,
"collect": 0,
"collect_count": 0
},
"children": [
{
"type": "org.elasticsearch.search.aggregations.metrics.avg.AvgAggregator",
"description": "avg_price",
"time_in_nanos": 5610,
"breakdown": {
"reduce": 0,
"build_aggregation": 0,
"build_aggregation_count": 0,
"initialize": 5609,
"initialize_count": 1,
"reduce_count": 0,
"collect": 0,
"collect_count": 0
}
}
]
}
]
} }
] ]
} }
] }
-------------------------------------------------- --------------------------------------------------
// TESTRESPONSE[s/\.\.\.//]
// TESTRESPONSE[s/: (\-)?[0-9]+/: $body.$_path/]
From the profile structure we can see our `property_type` terms aggregation which is internally represented by the From the profile structure we can see our `property_type` terms aggregation which is internally represented by the
`GlobalOrdinalsStringTermsAggregator` class and the sub aggregator `avg_price` which is internally represented by the `AvgAggregator` class. The `type` field displays the class used internally to represent the aggregation. The `description` field displays the name of the aggregation. `GlobalOrdinalsStringTermsAggregator` class and the sub aggregator `avg_price` which is internally represented by the `AvgAggregator` class. The `type` field displays the class used internally to represent the aggregation. The `description` field displays the name of the aggregation.
@ -772,12 +772,14 @@ The `breakdown` component lists detailed timing statistics about low-level Lucen
"reduce_count": 0, "reduce_count": 0,
"build_aggregation": 49765, "build_aggregation": 49765,
"build_aggregation_count": 300, "build_aggregation_count": 300,
"initialise": 52785, "initialize": 52785,
"initialize_count": 300, "initialize_count": 300,
"reduce_count": 0,
"collect": 3155490036, "collect": 3155490036,
"collect_count": 1800 "collect_count": 1800
} }
-------------------------------------------------- --------------------------------------------------
// NOTCONSOLE
Timings are listed in wall-clock nanoseconds and are not normalized at all. All caveats about the overall Timings are listed in wall-clock nanoseconds and are not normalized at all. All caveats about the overall
`time` apply here. The intention of the breakdown is to give you a feel for A) what machinery in Elasticsearch is `time` apply here. The intention of the breakdown is to give you a feel for A) what machinery in Elasticsearch is