Skip to content

Conversation

@rjernst
Copy link
Member

@rjernst rjernst commented Feb 26, 2015

This has been deprecated since 1.0.0.RC1. It is finally removed here.

closes #8875

@jpountz
Copy link
Contributor

jpountz commented Feb 26, 2015

It seems to me that with this change we would fail to parse mappings that have a _boost, should we only do it on 2.x indices and ignore _boost on older indices?

@rjernst
Copy link
Member Author

rjernst commented Feb 26, 2015

@jpountz This actually already works. Any extra mapping elements found on indexes created before 2.0 are already ignored. Strict mapping checks (ie no leftover fields) are only enforced >= 2.0. I added this to the static bwc tests to verify.

@jpountz
Copy link
Contributor

jpountz commented Feb 26, 2015

Perfect then! LGTM

This has been deprecated since 1.0.0.RC1. It is finally removed here.

closes elastic#8875
@rjernst rjernst merged commit 7181bbd into elastic:master Feb 26, 2015
@spinscale spinscale added >breaking v2.0.0-beta1 :Search Foundations/Mapping Index mappings, including merging and defining field types labels Mar 4, 2015
@rjernst rjernst deleted the pr/8875 branch March 24, 2015 03:18
@clintongormley clintongormley changed the title Mappings: Remove _boost field Remove _boost field Jun 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>breaking :Search Foundations/Mapping Index mappings, including merging and defining field types v2.0.0-beta1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove the _boost field

3 participants