honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DOCS] Fix typo in profile API docs (#61445) (#61501) 

Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>

Co-authored-by: shashikumarec088 <shashikumarec088@gmail.com>
This commit is contained in:
James Rodewig 2020-08-24 15:30:18 -04:00 committed by GitHub
parent baa685c2d9
commit 2400098a52
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -302,7 +302,7 @@ by Lucene into a BooleanQuery with two clauses (both holding a TermQuery). The
`type` field displays the Lucene class name, and often aligns with the
equivalent name in Elasticsearch. The `description` field displays the Lucene
explanation text for the query, and is made available to help differentiating
between parts of your query (e.g. both `message:search` and `message:test` are
between parts of your query (e.g. both `message:get` and `message:search` are
TermQuery's and would appear identical otherwise.
The `time_in_nanos` field shows that this query took ~1.8ms for the entire
@ -310,8 +310,8 @@ BooleanQuery to execute. The recorded time is inclusive of all children.
The `breakdown` field will give detailed stats about how the time was spent,
we'll look at that in a moment. Finally, the `children` array lists any
sub-queries that may be present. Because we searched for two values ("search
test"), our BooleanQuery holds two children TermQueries. They have identical
sub-queries that may be present. Because we searched for two values ("get
search"), our BooleanQuery holds two children TermQueries. They have identical
information (type, time, breakdown, etc). Children are allowed to have their
own children.