Skip to content

Commit bed8737

Browse files
authored
[DOCS] Sync missing definitions from Elasticsearch glossary (#261)
1 parent ca3ca01 commit bed8737

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed

docs/en/glossary/glossary.asciidoc

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -185,6 +185,14 @@ local cluster. For more information, see {stack-ov}/xpack-ccr.html[{ccr-cap}].
185185
+
186186
//Source: X-Pack
187187
endif::xpack-terms[]
188+
ifdef::elasticsearch-terms[]
189+
[[glossary-ccs]] {ccs} (CCS)::
190+
191+
The {ccs} feature enables any node to act as a federated client across
192+
multiple clusters. See {ref}/modules-cross-cluster-search.html[{ccs-cap}].
193+
194+
//Source: Elasticsearch
195+
endif::elasticsearch-terms[]
188196
ifdef::xpack-terms[]
189197

190198
[[glossary-ml-datafeed]] datafeed ::
@@ -294,6 +302,20 @@ field: `[top-level field][nested field]`.
294302
+
295303
//Source: Logstash
296304
endif::logstash-terms[]
305+
ifdef::elasticsearch-terms[]
306+
307+
[[glossary-filter]] filter ::
308+
309+
A filter is a non-scoring <<glossary-query,query>>, meaning that it does not
310+
score documents. It is only concerned about answering the question - "Does this
311+
document match?". The answer is always a simple, binary yes or no. This kind of
312+
query is said to be made in a {ref}/query-filter-context.html[filter context], hence it
313+
is called a filter. Filters are simple checks for set inclusion or exclusion. In
314+
most cases, the goal of filtering is to reduce the number of documents that have
315+
to be examined.
316+
317+
//Source: Elasticsearch
318+
endif::elasticsearch-terms[]
297319
ifdef::logstash-terms[]
298320

299321
[[glossary-filter-plugin]] filter plugin ::
@@ -558,6 +580,21 @@ nodes handling the user requests.
558580
//Source: Cloud
559581
endif::cloud-terms[]
560582
ifdef::elasticsearch-terms[]
583+
[[glossary-query]] query ::
584+
585+
A query is the basic component of a search. A search can be defined by one or
586+
more queries which can be mixed and matched in endless combinations. While
587+
<<glossary-filter,filters>> are queries that only determine if a document
588+
matches, those queries that also calculate how well the document matches are
589+
known as "scoring queries". Those queries assign it a score, which is later used
590+
to sort matched documents. Scoring queries take more resources than
591+
<<glossary-filter,non scoring queries>> and their query results are not
592+
cacheable. As a general rule, use query clauses for full-text search or for any
593+
condition that requires scoring, and use filters for everything else.
594+
595+
//Source: Elasticsearch
596+
endif::elasticsearch-terms[]
597+
ifdef::elasticsearch-terms[]
561598

562599
[[glossary-recovery]] recovery ::
563600
The process of syncing a shard copy from a source shard. Upon completion, the recovery process makes the shard copy available for queries.

0 commit comments

Comments
 (0)