feat(search): Supporting Aggregations for hasX fields #8241
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.
Summary
In this PR, we introduce support for adding default aggregations returned in search queries for the Has X field extensions that we support in our @searchable annotations.
This will enable returning aggs for cases where it's important to understand a boolean rollup of a particular field. For example, to understand whether Assertions are failing for an asset, or whether an asset has owners, domains, glossary terms.
Also, added a new file for testing AggregationQueryBuilder. More tests will be necessary here.
Example
These changes add a few new fields to the Searchable annotation, which enable aggregation by default on the hasX existence extension fields:
Status
Ready for review
Checklist