Skip to content
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

Closed
kimchy opened this issue Mar 7, 2010 · 1 comment
Closed

Mapping - MultiField Mapping #51

kimchy opened this issue Mar 7, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Mar 7, 2010

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, once analyzed and one not_analyzed. For example:

{
    person : {
        properties : {
            "name" : {
                type : "multi_field",
                "fields" : {
                    "name" : {type: "string", index : "analyzed", store : "yes"},
                    "not_analyzed" : {type: "string", index : "not_analyzed"},
                }
            }
        }
    }
}

The above example, the name mapping is a multi field mapping. The name within the multi_field mapping is the "default" mapping (and used as if it was mapped regularly). The not_analyzed name is accessed through name.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.

@kimchy
Copy link
Member Author

kimchy commented Mar 7, 2010

Mapping - MultiField Mapping, closed by b13f6b1.

dadoonet added a commit that referenced this issue Jun 5, 2015
…galStateException` in favor of the JDK one

Related to #10794

Closes #51.
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
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
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…pull request elastic#51)

* admin-tools build: add node modules to tgz

Problem:
Running npm ci for all components for all sandboxes during first boot is
starting to take too long.

Solution:
Install and package node modules during build. Removee "npm ci" from
rc.local and update-engageli-sandboxes.sh

Approved-by: Rich Nessel
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
Projects
None yet
Development

No branches or pull requests

1 participant