Improve search filtering with server-side type aggregations and post_filter #2305
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
post_filterfor accurate aggregation countstypefield to return doc/api counts from the serverSearchRequest/SearchResponsetoSearchApiRequest/SearchApiResponseISearchGatewaywith newSearchResultrecordaggregations.typefor future extensibilitytypeFilterstate to search store for consistent filter state managementElasticsearchIngestChannelandElasticsearchMarkdownExporterinto partial files for better code organizationTechnical Details
Backend
ISearchGateway.SearchAsyncnow returnsSearchResultwithTotalHits,Results, andAggregationstypequery parameter (values:doc,api)post_filterensures aggregation counts reflect total matches regardless of active filterSearchAggregationsrecord wraps type counts for clean JSON structureFrontend
?type=parametertypeFilterfor proper result cachingcursorful-video-1764847637167.mp4