forked from elastic/kibana
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Obs AI Assistant] Ensure compatibility with the new semantic_text fo…
…rmat (elastic#206510) ## Summary Elasticsearch is introducing a breaking change in `8.18` and `9.0.0` to `semantic_text` fields. This PR ensures compatibility with this new `semantic_text` format. Relates to elastic/dev#2936 ### Changes made - Remove the `inference` meta field exclusions in recalling from semantic search connectors (the `inference` subfield won't be returned anymore with the new `semantic_text` format) - Set the `index.mapping.semantic_text.use_legacy_format` index setting to false to force the new format for KB indices and evaluation framework indices. The following does not impact Obs AI Assistant as a part of this breaking change: | Breaking change | Do we use it? | Is there an impact? | |--------|--------|--------| | `inner_hits` is removed and `highlight is introduced | We don't use `inner_hits` at the moment | No | | The shape of semantic text field return type is updated to a string (previously it was an object with a `text` property) | Even though we query via the `semantic_text` field in KB entries, we don't use the result of the `semantic_text` field in `_source` | No | | pre-computed embeddings using a new `_inference_fields` metafield | Not used | No | ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- Loading branch information
Showing
5 changed files
with
40 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters