honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-18 19:05:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

[Docs] Add missing annotation, fix blockdef

Browse Source
This commit is contained in:
Zachary Tong 2015-12-17 17:02:07 -05:00
parent b62f8f11d4
commit f5a992486e
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

@ -13,7 +13,7 @@ The output from the Profile API is *very* verbose, especially for complicated qu
many shards. Pretty-printing the response is recommended to help understand the output many shards. Pretty-printing the response is recommended to help understand the output
[NOTE] [NOTE]
--------------------- =======================================
The details provided by the Profile API directly expose Lucene class names and concepts, which means The details provided by the Profile API directly expose Lucene class names and concepts, which means
that complete interpretation of the results require fairly advanced knowledge of Lucene. This that complete interpretation of the results require fairly advanced knowledge of Lucene. This
page attempts to give a crash-course in how Lucene executes queries so that you can use the Profile API to successfully page attempts to give a crash-course in how Lucene executes queries so that you can use the Profile API to successfully
@ -23,7 +23,7 @@ to Lucene's documentation and, in places, the code.
With that said, a complete understanding is often not required to fix a slow query. It is usually With that said, a complete understanding is often not required to fix a slow query. It is usually
sufficient to see that a particular component of a query is slow, and not necessarily understand why sufficient to see that a particular component of a query is slow, and not necessarily understand why
the `advance` phase of that query is the cause, for example. the `advance` phase of that query is the cause, for example.
--------------------- =======================================
[float] [float]
=== Usage === Usage
@ -185,7 +185,7 @@ The overall structure of this query tree will resemble your original Elasticsear
"query_type": "BooleanQuery", "query_type": "BooleanQuery",
"lucene": "message:search message:test", "lucene": "message:search message:test",
"time": "15.52889800ms", "time": "15.52889800ms",
"breakdown": {...}, "breakdown": {...}, <1>
"children": [ "children": [
{ {
"query_type": "TermQuery", "query_type": "TermQuery",