-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Mapping - MultiField Mapping #51
Comments
Mapping - MultiField Mapping, closed by b13f6b1. |
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
ywelsch
pushed a commit
to ywelsch/elasticsearch
that referenced
this issue
May 24, 2018
Today, if a node detects it is lagging the master it falls back to CANDIDATE but then receives a heartbeat from the master and goes back to FOLLOWER. If it is lagging because it missed a cluster state update for some reason then it will never recover, because there's no impetus to publish a further update. This change fixes this, crudely, by causing nodes to consider themselves as faulty while they are lagging, which eventually results in them being kicked out of the cluster and, later, rejoining, which fixes the lag. Fixes elastic#43, but will eventually be superseded by elastic#53.
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
Documentation Changes
dimitris-athanasiou
added a commit
that referenced
this issue
Feb 14, 2020
#52353) ML mappings and index templates have so far been created programmatically. While this had its merits due to static typing, there is consensus it would be clear to maintain those in json files. In addition, we are going to adding ILM policies to these indices and the component for a plugin to register ILM policies is `IndexTemplateRegistry`. It expects the templates to be in resource json files. For the above reasons this commit refactors ML mappings and index templates into json resource files that are registered via `MlIndexTemplateRegistry`. Backport of #51765
henningandersen
pushed a commit
to henningandersen/elasticsearch
that referenced
this issue
Jun 4, 2020
With this commit we specify an index template and use a matching index in all bulk-size evaluation challenges. Due to restrictions with the maximum number of clients we also reduce the number of concurrent clients from 200 to 100 in the concurrency challenge. Relates elastic#51
This was referenced Sep 26, 2022
Closed
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
Also use shlex.quote for safely generating cli arguments passed to Rally instead of enclosing them in `\"{}\"`. Relates elastic#62 Closes elastic#51
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add another type
multi_field
for mapping to support mapping more than one core type. This is handy, for example, to map the same string type, onceanalyzed
and onenot_analyzed
. For example:The above example, the
name
mapping is a multi field mapping. Thename
within themulti_field
mapping is the "default" mapping (and used as if it was mapped regularly). Thenot_analyzed
name is accessed throughname.not_analyzed
, and it won't be analyzed.A special case is when merging, upgrading core type mapping into multi field mapping if the new mapping set for this property is now multi mapping.
The text was updated successfully, but these errors were encountered: