Fixes non-bucket based aggregations throwing exception #216
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
quintenbuis
force-pushed
the
support-non-bucket-based-aggregations
branch
from
7ff0225
to
5da9305
Compare
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.
Currently using the
MaxAggregationthrows an exception because thebucketskey cannot be found, which is correct because according to the docs the max aggregation doesn't have abucketskey.The
The fix:
When the above scenario happens it will dump the raw aggregation data as the
AggregationResult->values.Notes
I'm aware it isn't the cleanest of implementations, but this way it ensures backwards compatibility.