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.

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

[ZDT] migration algorithm follow-up #161067

Closed
2 of 3 tasks
pgayvallet opened this issue Jul 3, 2023 · 2 comments
Closed
2 of 3 tasks

[ZDT] migration algorithm follow-up #161067

pgayvallet opened this issue Jul 3, 2023 · 2 comments
Labels
Feature:Migrations Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@pgayvallet
Copy link
Contributor

pgayvallet commented Jul 3, 2023

Follow-up of #150309
Part of #150296

Follow-up / optimizations:

@pgayvallet pgayvallet added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:Migrations labels Jul 3, 2023
@elasticmachine
Copy link
Contributor

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

gsoldevila added a commit that referenced this issue Jul 4, 2023
Part of #161067

Same idea as #159962, but applied
to ZDT.

When "picking up" the updated mappings, we add a "query" in order to
select and update only the SO types that have been updated, compared to
the previous version.
@pgayvallet
Copy link
Contributor Author

I'm going to close this - the two optional points have been addressed, and we decided that the last one isn't going to be mandatory short or mid term, as we're not planning on adding any core migration version anytime soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Migrations Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

2 participants