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 Overhaul - More user friendly, cluster aware #34

Closed
kimchy opened this issue Feb 21, 2010 · 7 comments
Closed

Mapping Overhaul - More user friendly, cluster aware #34

kimchy opened this issue Feb 21, 2010 · 7 comments

Comments

@kimchy
Copy link
Member

kimchy commented Feb 21, 2010

  1. When adding mapping definitions, they are now merged with the current mapping definitions. Duplicates are silently ignore unless specified in the put mapping API (HTTP param ignoreDuplicates set to false). Note, duplicates refer only to field mapping, object mapping are recursively checked.
  2. Mappings definitions are now clustered. Up until now, when creating mapping, the mappings were not merged (see point 1) but they were broadcasted to the cluster. But, when a document indexed resulted in updated mapping, this fact was lost. Now, this changed mapping are updated on the master and merged, and broadcasted to the whole cluster, which means all the different nodes will know about the new types introduced almost immediately.
@kimchy
Copy link
Member Author

kimchy commented Feb 21, 2010

Note, I renamed create mapping to be named put mapping since it reflects the API better. The rest API is the same, the site docs will be updated.

@kimchy
Copy link
Member Author

kimchy commented Feb 21, 2010

Mapping Overhaul - More user friendly, cluster aware, closed by 6d52065.

@kimchy
Copy link
Member Author

kimchy commented Mar 1, 2010

Renamed ignoreDuplicates to ignoreConflicts.

@clintongormley
Copy link

The current version on github still uses ignoreDuplicates, not ignoreConflicts

@kimchy
Copy link
Member Author

kimchy commented Mar 2, 2010

You sure? Http request parameter parsed is ignoreConflicts, and defaults to true.

@clintongormley
Copy link

Apologies - my update failed because you changed 'devRelease' to 'release' and I didn't see it.

it does work now ++

@kimchy
Copy link
Member Author

kimchy commented Mar 2, 2010

Yea, sorry about that. Just run gradlew without anything, it will default to building things properly always.

dadoonet added a commit that referenced this issue Jun 5, 2015
Closes #34.

(cherry picked from commit ddd941b)
dadoonet pushed a commit that referenced this issue Jun 5, 2015
Closes #34.

(cherry picked from commit e149f70)
dadoonet added a commit that referenced this issue Jun 5, 2015
Introduced in #7336 (elasticsearch 1.4 and 2.0), we need to change AzureDiscovery constructor.

Closes #34.
johtani added a commit that referenced this issue Jun 5, 2015
johtani added a commit that referenced this issue Jun 5, 2015
johtani added a commit that referenced this issue Jun 5, 2015
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
FastByteArrayInputStream has been removed in 0.90.3.
Closes elastic#34.
ywelsch added a commit to ywelsch/elasticsearch that referenced this issue May 24, 2018
Implements the alternative "Zen with terms but without slots" model formalized in
elastic/elasticsearch-formal-models#30
ClaudioMFreitas pushed a commit to ClaudioMFreitas/elasticsearch-1 that referenced this issue Nov 12, 2019
Support for Node configuration, Roles and Multiple Nodes Per Machine
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
and commit bulk-update challenge

Relates elastic#34
williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…ic#34)

change tag_all to work with wsl

* change tag_all to work with wsl
stu-elastic pushed a commit to stu-elastic/elasticsearch that referenced this issue Nov 2, 2023
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

2 participants