[Obs AI Assistant] Remove semantic_text migration#220886
[Obs AI Assistant] Remove semantic_text migration#220886sorenlouv merged 21 commits intoelastic:mainfrom
Conversation
|
Pinging @elastic/obs-ai-assistant (Team:Obs AI Assistant) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
x-pack/platform/plugins/shared/observability_ai_assistant/server/service/inference_endpoint.ts
Outdated
Show resolved
Hide resolved
| const LOCK_ID = 'my_lock_with_lock'; | ||
|
|
||
| describe('Successful execution and concurrent calls', () => { | ||
| let executions: number; |
There was a problem hiding this comment.
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 🤞
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. |
...stic/apis/observability/ai_assistant/knowledge_base/knowledge_base_8.16_upgrade_test.spec.ts
Show resolved
Hide resolved
x-pack/platform/plugins/shared/observability_ai_assistant/server/service/client/index.ts
Outdated
Show resolved
Hide resolved
x-pack/platform/plugins/shared/observability_ai_assistant/server/service/client/index.ts
Outdated
Show resolved
Hide resolved
…er/service/client/index.ts Co-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>
…er/service/client/index.ts Co-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
History
|
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. |
## 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 <viduni.ushanka@gmail.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
## 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 <viduni.ushanka@gmail.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
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: