-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Support semantic_text in ES|QL #115103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Pinging @elastic/es-search (Team:Search) |
Pinging @elastic/kibana-esql (ES|QL-ui) |
Pinging @elastic/es-search-relevance (Team:Search Relevance) |
Since field caps will report After the field caps change is merged, we might need to go back and clean up some of the changes that specifically accounted for a |
closing this issue - we do have an outstanding issue with #115166 that does not allow us to test semantic search in ES|QL with mixed version clusters. we do test for single-node/multi-node clusters and the rest of the follow ups have been addressed so I think we can just close this one. |
Uh oh!
There was an error while loading. Please reload this page.
This meta issue tracks adding support for
semantic_text
to ES|QL.match
function Semantic search with query builder rewrite #118676semantic_text
such 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_text
fields in the same way we usekeyword
andtext
and be able to passsemantic_text
field to any function/operator that can accept string fields.Follow-ups:
mapping-all-types.json
and test semantic-text fields withinLocalPhysicalPlanOptimizerTests.java
Semantic 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)The text was updated successfully, but these errors were encountered: