Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[meta] Kibana managed upgrades #150296

Closed
pgayvallet opened this issue Feb 6, 2023 · 2 comments
Closed

[meta] Kibana managed upgrades #150296

pgayvallet opened this issue Feb 6, 2023 · 2 comments
Labels
Epic:ZDTmigrations Zero downtime migrations Feature:Migrations Meta Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@pgayvallet
Copy link
Contributor

pgayvallet commented Feb 6, 2023 •
edited
Loading

This is a meta issue to track the work required for managed upgrades

First phase

Second phase

Testing plan for ZDT migrations

  • [tbd]
@botelastic botelastic bot added the needs-team Issues missing a team label label Feb 6, 2023
@pgayvallet pgayvallet added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Meta Feature:Migrations Epic:ZDTmigrations Zero downtime migrations and removed needs-team Issues missing a team label labels Feb 6, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@pgayvallet pgayvallet changed the title Kibana managed upgrades [meta] Kibana managed upgrades Feb 6, 2023
This was referenced Feb 6, 2023
Closed
Closed
Closed
Closed
@pgayvallet pgayvallet mentioned this issue May 16, 2023
Closed
3 tasks
@pgayvallet pgayvallet mentioned this issue May 30, 2023
Merged
pgayvallet added a commit that referenced this issue May 31, 2023
@pgayvallet
[ZDT] use range clause for outdated doc query (#158651)
c20566d 
## Summary

Related to #150296

Use a `range` clause for version filtering for the ZDT outdated doc
query, similar to what is already done for the `v2` algo, to avoid
eventually trying to migrate documents from higher versions (which would
result in a migration failure)
This was referenced Jul 3, 2023
Closed
Merged
Merged
pgayvallet added a commit that referenced this issue Jul 5, 2023
@pgayvallet
[ZDT] support registering new types (#161255)
833410b 
## Summary

Related to #150296

Fix a bug causing the ZDT migration algorithm to fail when a new type
gets introduced between two versions.
pgayvallet added a commit that referenced this issue Jul 7, 2023
@pgayvallet @kibanamachine
[modelVersions] add new migration change types (#161147)
52eb488 
## Summary

Related to #150296

- Add the following SO model version change types:
  - `data_removal`
  - `unsafe_transform`
- Change the existing `data_backfill` type to something less permissive
- Update the tsdoc and documentation accordingly

---------

Co-authored-by: Kibana Machine <[email protected]>
@rayafratkina
Copy link
Contributor

This work is done, closing this meta issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Epic:ZDTmigrations Zero downtime migrations Feature:Migrations Meta Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pgayvallet @elasticmachine @rayafratkina