Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: django-haystack/django-haystack
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: rw-spot/django-haystack
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 1 file changed
  • 1 contributor

Commits on Oct 15, 2014

  1. ElasticSearch geo-filters with explicit units. 

    Fix an issue where distance filtering (using `dwithin`) passed an
ambiguous argument, leading to incorrect distance filtering.

The ElasticSearch backend passed an unlabeled float that was known to
represent the given distance in kilometers. However, ElasticSearch
server's default unit for distance filtering is the meter. Thus, in
deployments with no change to the default unit, these query values were
interpreted as meter values.

An example of this bad behavior is that when a user filtered for items
within 1 kilometer of a query point, she would actually get only items
within 1 meter of the query point.
    @rw
    rw committed Oct 15, 2014
    Configuration menu
    Copy the full SHA
    0808bcd View commit details
    Browse the repository at this point in the history
Loading