Geo_distance agg results not consistent

I was trying out the geo_distance aggreation and received different results based on the order of the ranges specified. I was able to replicate this using the example in the geo_distance aggregation documentation page.

PUT /museums
{
  "mappings": {
    "properties": {
      "location": {
        "type": "geo_point"
      }
    }
  }
}

POST /museums/_bulk?refresh
{"index":{"_id":1}}
{"location": "POINT (4.912350 52.374081)", "name": "NEMO Science Museum"}
{"index":{"_id":2}}
{"location": "POINT (4.901618 52.369219)", "name": "Museum Het Rembrandthuis"}
{"index":{"_id":3}}
{"location": "POINT (4.914722 52.371667)", "name": "Nederlands Scheepvaartmuseum"}
{"index":{"_id":4}}
{"location": "POINT (4.405200 51.222900)", "name": "Letterenhuis"}
{"index":{"_id":5}}
{"location": "POINT (2.336389 48.861111)", "name": "Musée du Louvre"}
{"index":{"_id":6}}
{"location": "POINT (2.327000 48.860000)", "name": "Musée d'Orsay"}

And then submit the following two queries...

POST /museums/_search?size=0
{
  "aggs": {
    "rings_around_amsterdam": {
      "geo_distance": {
        "field": "location",
        "origin": "POINT (4.894 52.3760)",
        "ranges": [
          { "to": 100000 },
          { "from": 100000, "to": 300000 },
          { "from": 300000 }
        ]
      }
    }
  }
}

I get document counts in my agg buckets of 3, 1, and 2.

If I change just the order of the ranges in the query to this:

POST /museums/_search?size=0
{
  "aggs": {
    "rings_around_amsterdam": {
      "geo_distance": {
        "field": "location",
        "origin": "POINT (4.894 52.3760)",
        "ranges": [
          { "from": 100000, "to": 300000 },
          { "from": 300000 },
          { "to": 100000 }
        ]
      }
    }
  }
}

I get document counts in my agg buckets of 1, 2, and 0.

I was thinking the order of the ranges would not matter. Am I missing something?

Hi @drfreed!

Welcome to the community, this is clearly a bug, results should be independent of the ordering of the provided ranges. Would you mind opening a bug report in the Elasticsearch repository?

Sure, I will put one in... thanks!