Skip to content

Default Mappings #87

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.

Sign up for GitHub

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

Jump to bottom
Closed
BubDZombie opened this issue Mar 24, 2010 · 3 comments
Closed

Default Mappings #87

BubDZombie opened this issue Mar 24, 2010 · 3 comments

Comments

@BubDZombie
Copy link

Allow for the creation of mappings that will be inherited when new indices are created, specifically when an index PUT request is made for an index that doesn't exist yet.
@saden1
Copy link

saden1 commented Jan 10, 2013

I just wanted to clarify if this issue still holds true and if there is any intention to fix it.

Say I have a default mappings file that specifies a field called "content" and I also create a mappings file for an index called "posts" that does not define a "content" property. Is true that if I index a document that contains the property "content" to the "posts" index the default mappings definition of this "content" property will be ignored?

@imotov
Copy link
Contributor

imotov commented Jan 10, 2013

@saden1 if you will define a property called "content" in the default mapping, this property will be added automatically for every mapping that doesn't define it.

@imotov
Copy link
Contributor

imotov commented Jan 10, 2013

This issue is addressed with Index and Dynamic Templates. Closing.

@imotov imotov closed this as completed Jan 10, 2013
@bluelu bluelu mentioned this issue Dec 11, 2014
Closed
imotov added a commit that referenced this issue Jun 5, 2015
@imotov @dadoonet
Switch to shared thread pool for snapshot operations
d322b10 
Closes #87

(cherry picked from commit 36d4da6)
@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
@dadoonet
Tests: AnalysisService constructor signature change
c3bf3b1 
Due to this [change](elastic#8018), we need to fix our tests for elasticsearch 1.4.0 and above.

Closes elastic#87.

(cherry picked from commit b3b0d34)
@nachogiljaldo nachogiljaldo mentioned this issue Aug 31, 2017
Closed
@nachogiljaldo nachogiljaldo mentioned this issue Aug 24, 2018
Closed
ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
Merge pull request elastic#87 from gingerwizard/master
83303e4 
Correct Error detection for plugin install and check logging.yml is removed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@BubDZombie @imotov @saden1