mirror of
https://github.com/elastic/kibana.git
synced 2025-06-27 10:40:07 -04:00
8efc526314
## Summary * Address https://github.com/elastic/kibana/issues/217145 - Put in place a check to ensure we're upgrading from Kibana 8.18.0 or newer. * Address https://github.com/elastic/kibana/issues/220521 - New attempt at removing the `switchToModelVersionAt` property, inspired on https://github.com/elastic/kibana/pull/219029. The previous attempt caused a regression: index meta information started storing _modelVersions_ that were older than the previously stored ones, which were defaulting to 10.0.0 for SO types that did NOT define `modelVersions`. This was due to the removal of the applyTypeDefaults, which was ensuring all SOs had the `switchToModelVersionAt` property set. This flag was then used by `src/core/packages/saved-objects/base-server-internal/src/model_version/version_map.ts` to determine whether to use `modelVersions` or the legacy `migrations` property in order to determine the latest model version for a given type. When removing the `switchToModelVersionAt` flag (and its default backfill), the logic started defaulting to the latest `migrations` version for those SO types that were not defining any `modelVersion`, resulting in older versions that those stored in the SO indices. This caused incident https://elasticco.atlassian.net/browse/INC-3818. This regression has been shipped in 9.0.0 (the PR was [backported](https://github.com/elastic/kibana/pull/219329)), so in top of the cleanup, we now need to address https://github.com/elastic/kibana/issues/220521 to ensure a smooth transition _OnPrem => Serverless_. --------- Co-authored-by: Christiane (Tina) Heiligers <christiane.heiligers@elastic.co> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| development/plugins/expressions/public | ||
| extend | ||
| reference | ||
| release-notes | ||
| settings-gen | ||
| CHANGELOG.asciidoc | ||
| docset.yml | ||