Skip to content

Conversation

@sorenlouv
Copy link
Member

@sorenlouv sorenlouv commented May 18, 2025

Background

The semantic text migration was added in 8.17 along with the move to semantic_text field (#186499).

Suggestion

We should remove the semantic_text migration starting in 9.1. Reasons:

  • The migration has recently caused severe disruption on a number of clusters ([Obs AI Assistant] Use update-by-query for semantic_text migration #220255).
  • The migration may no longer be needed. Users are required to upgrade Elasticsearch to 8.18 in order to update to 9.0, or 8.19 to upgrade to 9.1. This could mean that users are guaranteed to have run the migration previously, when upgrading Kibana to 9.1 (needs to be double checked with Kibana folks)

@sorenlouv sorenlouv marked this pull request as ready for review May 22, 2025 14:17
@sorenlouv sorenlouv requested a review from a team as a code owner May 22, 2025 14:17
@botelastic botelastic bot added ci:project-deploy-observability Create an Observability project Team:Obs AI Assistant Observability AI Assistant labels May 22, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ai-assistant (Team:Obs AI Assistant)

@github-actions
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@sorenlouv sorenlouv requested a review from a team as a code owner May 22, 2025 21:20
@sorenlouv sorenlouv enabled auto-merge (squash) May 23, 2025 21:39
@sorenlouv sorenlouv disabled auto-merge May 23, 2025 21:39
const LOCK_ID = 'my_lock_with_lock';

describe('Successful execution and concurrent calls', () => {
let executions: number;
Copy link
Member Author

@sorenlouv sorenlouv May 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not related but this test was flaky (failed 1 out of 100 runs). The changes here should improve it - still waiting for flaky test runner to complete 🤞

@kibanamachine
Copy link
Contributor

Flaky Test Runner Stats

🟠 Some tests failed. - kibana-flaky-test-suite-runner#8298

[✅] x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.ai_assistant.serverless.config.ts: 100/100 tests passed.
[❌] x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.stateful.config.ts: 74/100 tests passed.

see run history

@sorenlouv sorenlouv enabled auto-merge (squash) May 27, 2025 22:04
@elasticmachine
Copy link
Contributor

elasticmachine commented May 28, 2025

💛 Build succeeded, but was flaky

  • Buildkite Build
  • Commit: 369cbf3
  • Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-220886-369cbf329a6b

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #28 / Actions and Triggers app Stack alerts page Loads the page with actions but not alerting privilege Loads the page but shows missing permission prompt

Metrics [docs]

✅ unchanged

History

@sorenlouv sorenlouv merged commit b4767bb into elastic:main May 28, 2025
11 checks passed
@sorenlouv sorenlouv deleted the remove-semantic-text-migration branch May 28, 2025 11:27
@kibanamachine
Copy link
Contributor

Flaky Test Runner Stats

🎉 All tests passed! - kibana-flaky-test-suite-runner#8305

[✅] x-pack/test/api_integration/deployment_agnostic/configs/serverless/oblt.ai_assistant.serverless.config.ts: 100/100 tests passed.
[✅] x-pack/test/api_integration/deployment_agnostic/configs/stateful/oblt.ai_assistant.stateful.config.ts: 100/100 tests passed.

see run history

akowalska622 pushed a commit to akowalska622/kibana that referenced this pull request May 29, 2025
## Background
The semantic text migration was added in 8.17 along with the move to
semantic_text field (elastic#186499).

## Suggestion

We should remove the semantic_text migration starting in 9.1. Reasons:

- The migration has recently caused severe disruption on a number of
clusters (elastic#220255).
- The migration may no longer be needed. Users are required to upgrade
Elasticsearch to 8.18 in order to update to 9.0, or 8.19 to upgrade to
9.1. This could mean that users are guaranteed to have run the migration
previously, when upgrading Kibana to 9.1 (needs to be double checked
with Kibana folks)

---------

Co-authored-by: Viduni Wickramarachchi <[email protected]>
Co-authored-by: kibanamachine <[email protected]>
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label May 30, 2025
@kibanamachine
Copy link
Contributor

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 220886 locally
cc: @sorenlouv

@sorenlouv sorenlouv added the backport:skip This PR does not require backporting label May 30, 2025
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label May 30, 2025
@sorenlouv sorenlouv added backport missing Added to PRs automatically when the are determined to be missing a backport. and removed backport:version Backport to applied version labels labels May 30, 2025
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label May 30, 2025
zacharyparikh pushed a commit to zacharyparikh/kibana that referenced this pull request Jun 4, 2025
## Background
The semantic text migration was added in 8.17 along with the move to
semantic_text field (elastic#186499).

## Suggestion

We should remove the semantic_text migration starting in 9.1. Reasons:

- The migration has recently caused severe disruption on a number of
clusters (elastic#220255).
- The migration may no longer be needed. Users are required to upgrade
Elasticsearch to 8.18 in order to update to 9.0, or 8.19 to upgrade to
9.1. This could mean that users are guaranteed to have run the migration
previously, when upgrading Kibana to 9.1 (needs to be double checked
with Kibana folks)

---------

Co-authored-by: Viduni Wickramarachchi <[email protected]>
Co-authored-by: kibanamachine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip This PR does not require backporting ci:project-deploy-observability Create an Observability project release_note:enhancement Team:Obs AI Assistant Observability AI Assistant v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants