Skip to content

[DOCS] Sync missing definitions from Elasticsearch glossary #261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 29, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 37 additions & 0 deletions docs/en/glossary/glossary.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -185,6 +185,14 @@ local cluster. For more information, see {stack-ov}/xpack-ccr.html[{ccr-cap}].
+
//Source: X-Pack
endif::xpack-terms[]
ifdef::elasticsearch-terms[]
[[glossary-ccs]] {ccs} (CCS)::

The {ccs} feature enables any node to act as a federated client across
multiple clusters. See {ref}/modules-cross-cluster-search.html[{ccs-cap}].

//Source: Elasticsearch
endif::elasticsearch-terms[]
ifdef::xpack-terms[]

[[glossary-ml-datafeed]] datafeed ::
Expand Down Expand Up @@ -286,6 +294,20 @@ field: `[top-level field][nested field]`.
+
//Source: Logstash
endif::logstash-terms[]
ifdef::elasticsearch-terms[]

[[glossary-filter]] filter ::

A filter is a non-scoring <<glossary-query,query>>, meaning that it does not
score documents. It is only concerned about answering the question - "Does this
document match?". The answer is always a simple, binary yes or no. This kind of
query is said to be made in a {ref}/query-filter-context.html[filter context], hence it
is called a filter. Filters are simple checks for set inclusion or exclusion. In
most cases, the goal of filtering is to reduce the number of documents that have
to be examined.

//Source: Elasticsearch
endif::elasticsearch-terms[]
ifdef::logstash-terms[]

[[glossary-filter-plugin]] filter plugin ::
Expand Down Expand Up @@ -550,6 +572,21 @@ nodes handling the user requests.
//Source: Cloud
endif::cloud-terms[]
ifdef::elasticsearch-terms[]
[[glossary-query]] query ::

A query is the basic component of a search. A search can be defined by one or
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These feel more verbose than I'd expect for a glossary entry, but I guess it doesn't matter too much.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree. I think a rewrite is probably in order. Query isn't actually defined here IMO.

I opened elastic/elasticsearch#40643 to address that separately. I'm planning on doing a general query overhaul shortly. That issue will likely be a part of that work effort.

more queries which can be mixed and matched in endless combinations. While
<<glossary-filter,filters>> are queries that only determine if a document
matches, those queries that also calculate how well the document matches are
known as "scoring queries". Those queries assign it a score, which is later used
to sort matched documents. Scoring queries take more resources than
<<glossary-filter,non scoring queries>> and their query results are not
cacheable. As a general rule, use query clauses for full-text search or for any
condition that requires scoring, and use filters for everything else.

//Source: Elasticsearch
endif::elasticsearch-terms[]
ifdef::elasticsearch-terms[]

[[glossary-reindex]] reindex ::

Expand Down