Elasticsearch backend using incorrect coordinates for geo_bounding_box (within) filter #670
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
…d bottom_right (southeast). Haystack's elasticsearch backend is passing northeast and southwest coordinates instead.
jezdez
added a commit
that referenced
this pull request
Nov 28, 2012
Elasticsearch backend using incorrect coordinates for geo_bounding_box (within) filter
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.
Elasticsearch geo_bounding_box filter expects top_left (northwest) and bottom_right (southeast).
Haystack's elasticsearch backend is passing northeast and southwest coordinates instead.