-
Notifications
You must be signed in to change notification settings - Fork 25.8k
ES|QL - Improve performance of V_MAGNITUDE function #137535
Copy link
Copy link
Open
Labels
:Analytics/ES|QLAKA ESQLAKA ESQL:Search Relevance/ES|QLSearch functionality in ES|QLSearch functionality in ES|QL>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>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.
V_MAGNITUDEfunction is not currently pushed down to Lucene. We want V_MAGNITUDE to be on par with the other vector functions, and be able to be pushed down to Lucene for performance reasons.See #137002 for the work done on vector similarity functions.