[Security Solution][AI Assistant] Revert conversation mappings changes#233428

Merged

spong merged 3 commits intoelastic:mainfrom

e40pud:security/genai/conversations/revert-mappings

Aug 29, 2025

Contributor

e40pud commented Aug 29, 2025

Summary

Epic: https://github.com/elastic/security-team/issues/12768
Meta: https://github.com/elastic/security-team/issues/13657
RFC: internal link

This PR reverts conversation mappings changes introduced in #232288. Since we decided to put on hold the Using Past Conversation as Context feature, we decided to remove added summary field backed by the semantic_text field to avoid potential issues that users mights have when updating a conversation while the inference endpoint is not available.

Changes:

Removed mapping fields: semantic_content and summarized_message_ids
As part of these changes, the summary field was hidden on the API level and conversations response object won't have it anymore


          [Security Solution][AI Assistant] Revert conversation mappings changes

6c89c6b

e40pud added this to the 9.2 milestone

e40pud self-assigned this

e40pud added the release_note:skip label

e40pud requested a review from a team as a code owner

August 29, 2025 07:44

e40pud added Team: SecuritySolution Team:Security Generative AI backport:version v9.2.0 labels

Contributor

elasticmachine commented Aug 29, 2025

Pinging @elastic/security-solution (Team: SecuritySolution)

e40pud requested a review from spong

August 29, 2025 07:44

kibanamachine added 2 commits

August 29, 2025 08:01


          [CI] Auto-commit changed files from 'yarn openapi:bundle'

a6e5832


          [CI] Auto-commit changed files from 'make api-docs'

005de47

elastic-vault-github-plugin-prod bot requested a review from a team as a code owner

August 29, 2025 08:19

KDKHD reviewed

View reviewed changes

...elastic_assistant/server/ai_assistant_data_clients/conversations/field_maps_configuration.ts

                   array: false,
                   required: false,
                 },
+                'summary.content': {

Member

KDKHD Aug 29, 2025

So we will still keep this in the field map for now?

Contributor Author

e40pud Aug 29, 2025

These are the old mapping fields that we have to keep regardless whether we add new fields or not. They've been added to these mapping since beginning and will need to stay there for compatibility.

Contributor Author

e40pud Aug 29, 2025

In my previous PR, I moved these fields into a separate section, but now reverting to an original state.

Contributor

elasticmachine commented Aug 29, 2025

💚 Build Succeeded

Buildkite Build
Commit: 005de47

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
`@kbn/elastic-assistant-common`	688	681	-7

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`securitySolution`	10.2MB	10.2MB	-249.0B

Unknown metric groups

API count

id	before	after	diff
`@kbn/elastic-assistant-common`	804	796	-8

spong approved these changes

View reviewed changes

Member

spong left a comment

Pair reviewed -- thanks for the updates here @e40pud! LGTM! 👍

natasha-moore-elastic approved these changes

View reviewed changes

spong merged commit a5a93f3 into elastic:main

12 checks passed

ymao1 pushed a commit to ymao1/kibana that referenced this pull request


          [Security Solution][AI Assistant] Revert conversation mappings changes (

9d4781c

elastic#233428)

## Summary

Epic: elastic/security-team#12768
Meta: elastic/security-team#13657
RFC: [internal
link](https://docs.google.com/document/d/13jAJ5Q3_At_zAuwKjvpYehnM5uzKJSwZIZ1aJJNAf5k)

This PR reverts conversation mappings changes introduced in
elastic#232288. Since we decided to put
on hold the Using Past Conversation as Context feature, we decided to
remove added summary field backed by the `semantic_text` field to avoid
potential issues that users mights have when updating a conversation
while the inference endpoint is not available.

**Changes**:
* Removed mapping fields: `semantic_content` and
`summarized_message_ids`
* As part of these changes, the `summary` field was hidden on the API
level and conversations response object won't have it anymore

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

jkelas pushed a commit to jkelas/kibana that referenced this pull request


          [Security Solution][AI Assistant] Revert conversation mappings changes (

0ba8748

elastic#233428)

## Summary

Epic: elastic/security-team#12768
Meta: elastic/security-team#13657
RFC: [internal
link](https://docs.google.com/document/d/13jAJ5Q3_At_zAuwKjvpYehnM5uzKJSwZIZ1aJJNAf5k)

This PR reverts conversation mappings changes introduced in
elastic#232288. Since we decided to put
on hold the Using Past Conversation as Context feature, we decided to
remove added summary field backed by the `semantic_text` field to avoid
potential issues that users mights have when updating a conversation
while the inference endpoint is not available.

**Changes**:
* Removed mapping fields: `semantic_content` and
`summarized_message_ids`
* As part of these changes, the `summary` field was hidden on the API
level and conversations response object won't have it anymore

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

kibanamachine added the backport missing label

Contributor

kibanamachine commented Sep 2, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233428 locally
cc: @e40pud

4 similar comments

Contributor

kibanamachine commented Sep 3, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233428 locally
cc: @e40pud

Contributor

kibanamachine commented Sep 4, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233428 locally
cc: @e40pud

Contributor

kibanamachine commented Sep 5, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233428 locally
cc: @e40pud

Contributor

kibanamachine commented Sep 8, 2025

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233428 locally
cc: @e40pud

e40pud added backport:skip and removed backport:version labels

kibanamachine removed the backport missing label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip release_note:skip Team:Security Generative AI Team: SecuritySolution v9.2.0