Remove boost which is now unsupported #1313
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@chrisbrooke Are there any downsides to doing this for ElasticSearch <2.0, which is still pretty common (e.g. AWS's ElasticSearch service runs 1.5) |
|
@acdha according to the docs _boost has been deprecated in Elasticsearch as of v1.0.0.RC1 (https://www.elastic.co/guide/en/elasticsearch/reference/1.4/mapping-boost-field.html#function-score-instead-of-boost). Boost can still be supplied on a field level by adding the boost value to the seach_index |
acdha
added a commit
that referenced
this pull request
Feb 17, 2016
…data-changes ElasticSearch: remove deprecated boost mapping section Thanks to @chrisbrooke for the patch
|
Perfect – thanks for checking! |
acdha
added a commit
to acdha/django-haystack
that referenced
this pull request
Mar 25, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In Elasticsearch >2.0, boost is no longer a support meta-data:
https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_mapping_changes.html#migration-meta-fields
See: http://stackoverflow.com/questions/35443179/django-haystack-locationfield-created-as-string-instead-of-geo-point-in-elastics