|
|
@@ -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.
|
|
|
|
James Rodewig