-
Notifications
You must be signed in to change notification settings - Fork 25.2k
_all field #63
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
Comments
_all field, closed by 1dd5997. |
IanvsPoplicola
pushed a commit
to IanvsPoplicola/elasticsearch
that referenced
this issue
Mar 21, 2017
Update Coordination.md
ywelsch
pushed a commit
to ywelsch/elasticsearch
that referenced
this issue
Jun 4, 2018
Rethrowing a FailedToCommitClusterStateException is the wrong thing to do - it should be passed to the listener for further processing.
ywelsch
pushed a commit
to ywelsch/elasticsearch
that referenced
this issue
Jun 4, 2018
A consequence of elastic#63 is that a FailedToCommitClusterStateException is no longer thrown by ZenDiscovery#publish(), it is just passed to the listener, so tests that relied on catching it can no longer work.
ywelsch
pushed a commit
to ywelsch/elasticsearch
that referenced
this issue
Jun 4, 2018
A consequence of elastic#63 is that a FailedToCommitClusterStateException is no longer thrown by ZenDiscovery#publish(), it is just passed to the listener, so tests that relied on catching it can no longer work.
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
henningandersen
pushed a commit
to henningandersen/elasticsearch
that referenced
this issue
Jun 4, 2020
With this commit we expose the track parameter `bulk_size` for the challenge `index-logs-fixed-daily-volume`. This also eliminates the need for the challenges `bulk-size-evaluation`, `bulk-size-evaluation-mini` and `bulk-size-concurrency-evaluation` as they can be simulated using the track parameters `bulk_size` and `bulk_indexing_clients`.
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we remove the cluster health check for x-pack because recent Rally versions only test for cluster health of indices that are created during the benchmark instead of all indices (e.g. `.security`). Thus, the cluster health check is also green when x-pack is enabled. Relates elastic#63
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Support
_all
field. The idea of an_all
field is a field that includes the text of one or more other fields within the document indexed. It can come very handy especially for search request, where we want to execute a search query against the content of a document, without knowing which fields to search on. This comes at the expense of CPU cycles and index size.The all fields can be completely disabled. Explicit field mapping and object mapping can be excluded / included in the all field. By default, all field is enabled and all fields are included in it for ease of use.
One of the nice features of the all field is that it takes into account specific fields boost levels. Meaning that if a
title
field is boosted more thancontent
, thetitle
(part) in the_all
field will mean more than thecontent
part in theall
field.With the
_all
field, certain APIs that require fields to be set can be simplified. They include:queryString
querydefaultField
now defaults to the_all
field.terms
APIfields
now default to the_all
field and not required._all
if not set.Here is a sample mapping:
The
allField
mapping can also be associated with an analyzer (index/search), atermVector
, and the ability tostore
it (the concatenated text).The text was updated successfully, but these errors were encountered: