-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Support semantic_text in ES|QL #115103
Copy link
Copy link
Closed
Labels
:Search Relevance/SearchCatch all for Search RelevanceCatch all for Search RelevanceES|QL-uiImpacts ES|QL UIImpacts ES|QL UIMetaTeam:Search RelevanceMeta label for the Search Relevance team in ElasticsearchMeta label for the Search Relevance team in Elasticsearch
Metadata
Metadata
Assignees
Labels
:Search Relevance/SearchCatch all for Search RelevanceCatch all for Search RelevanceES|QL-uiImpacts ES|QL UIImpacts ES|QL UIMetaTeam: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.
This meta issue tracks adding support for
semantic_textto ES|QL.matchfunction Semantic search with query builder rewrite #118676semantic_textsuch that it has the same support as keyword and text which are simply seen as string fields:elasticsearch/x-pack/plugin/esql-core/src/main/java/org/elasticsearch/xpack/esql/core/type/DataType.java
Lines 356 to 358 in dcbbbab
With this change we will be able to use
semantic_textfields in the same way we usekeywordandtextand be able to passsemantic_textfield to any function/operator that can accept string fields.Follow-ups:
mapping-all-types.jsonand test semantic-text fields withinLocalPhysicalPlanOptimizerTests.javaSemantic search with query builder rewrite #118676 (comment)
fixed with Add semantic_text to mapping_all_types and switch to TranslationAware in PushFiltersToSource #118982
Refactor work (might be done separate from the semantic_text support project but tracking here):
look into whether we can do async mapping/physical planning using aBogdan made this happen 🎉 ESQL: introduce a pre-mapping logical plan processing step #121260CoordinatorMappingPreProcessor(from Esql expression lifecycle events proposal)