-
Notifications
You must be signed in to change notification settings - Fork 25.8k
ES|QL - Exclude dense_vector data from response by default #137532
Copy link
Copy link
Closed
Labels
:Analytics/ES|QLAKA ESQLAKA ESQL:Search Relevance/ES|QLSearch functionality in ES|QLSearch functionality in ES|QL:Search Relevance/SearchCatch all for Search RelevanceCatch all for Search Relevance>non-issueTeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)Team:Search RelevanceMeta label for the Search Relevance team in ElasticsearchMeta label for the Search Relevance team in Elasticsearch
Metadata
Metadata
Assignees
Labels
:Analytics/ES|QLAKA ESQLAKA ESQL:Search Relevance/ES|QLSearch functionality in ES|QLSearch functionality in ES|QL:Search Relevance/SearchCatch all for Search RelevanceCatch all for Search Relevance>non-issueTeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)Team:Search RelevanceMeta label for the Search Relevance team in ElasticsearchMeta label for the Search Relevance team in Elasticsearch
Type
Fields
Give feedbackNo fields configured for issues without a type.
ES|QL retrieves dense_vector data unless users explicitly remove it with DROP / KEEP. Users usually don't need dense_vector other than for debug purposes, so by default we should exclude it similar to #130382
dense_vector data will not be retrieved using ES|QL unless explicitly requested via KEEP or an EVAL command. It will behave by default as if DROP for all dense_vector fields had been requested.