[7.x] Adds support for geo-bounds filtering in geogrid aggregations#50996
Merged
talevy merged 2 commits intoelastic:7.xfrom Jan 14, 2020
Merged
[7.x] Adds support for geo-bounds filtering in geogrid aggregations#50996talevy merged 2 commits intoelastic:7.xfrom
talevy merged 2 commits intoelastic:7.xfrom
Conversation
…c#50002) It is fairly common to filter the geo point candidates in geohash_grid and geotile_grid aggregations according to some viewable bounding box. This change introduces the option of specifying this filter directly in the tiling aggregation. This is even more relevant to `geo_shape` where the bounds will restrict the shape to be within the bounds this optional `bounds` parameter is parsed in an equivalent fashion to the bounds specified in the geo_bounding_box query.
Collaborator
|
Pinging @elastic/es-analytics-geo (:Analytics/Geo) |
talevy
added a commit
to talevy/elasticsearch
that referenced
this pull request
Jan 14, 2020
Contributor
Author
|
run elasticsearch-ci/2 |
talevy
added a commit
to talevy/elasticsearch
that referenced
this pull request
Jan 14, 2020
talevy
added a commit
that referenced
this pull request
Jan 14, 2020
talevy
added a commit
that referenced
this pull request
Jan 14, 2020
SivagurunathanV
pushed a commit
to SivagurunathanV/elasticsearch
that referenced
this pull request
Jan 23, 2020
SivagurunathanV
pushed a commit
to SivagurunathanV/elasticsearch
that referenced
this pull request
Jan 23, 2020
…fter elastic#50996 (elastic#50997) after elastic#50996 (backport of elastic#50002) merged, the version guard on geo-grid `bounds` parameter can be updated to 7.6 re-enables bwc tests
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It is fairly common to filter the geo point candidates in
geohash_grid and geotile_grid aggregations according to some
viewable bounding box. This change introduces the option of
specifying this filter directly in the tiling aggregation.
This is even more relevant to
geo_shapewhere the bounds will restrictthe shape to be within the bounds
this optional
boundsparameter is parsed in an equivalent fashion tothe bounds specified in the geo_bounding_box query.
backport of #50002.