More REST tests for geo_bounds aggregation #94742
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
The cartesian_bounds tests were much more extensive, so we split them out and enhanched the geo_bounds test to cover the same scope.
With and without the wrap_longitude toggle
craigtaverner
added
>test
|
Pinging @elastic/es-analytics-geo (Team:Analytics) |
69 tasks
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.
The cartesian_bounds tests were much more extensive, so we split them out and enhanced the geo_bounds test to cover the same scope, and then added additional tests for crossing the dateline with the
wrap_longitudeflag, something that cartesian_bounds did not support.