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

Remove the _boost field #8875

Closed
clintongormley opened this issue Dec 10, 2014 · 2 comments · Fixed by #9897
Closed

Remove the _boost field #8875

clintongormley opened this issue Dec 10, 2014 · 2 comments · Fixed by #9897
Labels
>breaking :Search Foundations/Mapping Index mappings, including merging and defining field types Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch v2.0.0-beta1

Comments

@clintongormley
Copy link
Contributor

The _boost field was deprecated in 1.0.0.RC1 in favour of using the function_score query with an ordinary field. It should be removed in 2.0.0. Any mapping which includes a _boost field should be updated automatically to remove it.

Relates to #8870

@reuben-sutton
Copy link
Contributor

@clintongormley Is there a mechanism for automatically updating the mapping like this? I had a look, but couldn't figure it out.

@clintongormley
Copy link
Contributor Author

@reuben-sutton there isn't, currently

rjernst added a commit to rjernst/elasticsearch that referenced this issue Feb 26, 2015
This has been deprecated since 1.0.0.RC1. It is finally removed here.

closes elastic#8875
@rjernst rjernst removed the help wanted adoptme label Feb 26, 2015
@javanna javanna added the Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch label Jul 16, 2024
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 Team:Search Foundations Meta label for the Search Foundations team in Elasticsearch v2.0.0-beta1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants