Skip to content

Optimize significant_text aggregation to only parse the field it requires from _source#79651

Merged
benwtrent merged 1 commit intoelastic:masterfrom
benwtrent:feature/aggs-use-optimize-source-extraction
Nov 2, 2021
Merged

Optimize significant_text aggregation to only parse the field it requires from _source#79651
benwtrent merged 1 commit intoelastic:masterfrom
benwtrent:feature/aggs-use-optimize-source-extraction

Conversation

@benwtrent
Copy link
Copy Markdown
Member

Previously created optimizations:

Allow significant_text to only parse out the specific field it requires from _source. This allows for a minor optimization when _source is small, but can be significant (pun intended) when _source contains many fields, or other larger fields that significant_text doesn't care about.

Since significant_text does not allow sub-aggs, not caching the parsed _source is reasonable.

@elasticmachine elasticmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Oct 21, 2021
@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-analytics-geo (Team:Analytics)

@benwtrent benwtrent added v8.1.0 and removed v8.0.0 labels Nov 2, 2021
@benwtrent benwtrent merged commit 6608580 into elastic:master Nov 2, 2021
@benwtrent benwtrent deleted the feature/aggs-use-optimize-source-extraction branch November 2, 2021 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Analytics/Aggregations Aggregations >enhancement Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v8.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants