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

[UA] Add reindex warning for mapping type changes #32081

Merged
merged 2 commits into from
Mar 13, 2019

Conversation

joshdover
Copy link
Contributor

Summary

This adds a warning to the reindex process that will display when the user is reindexing an index that does not use a type name of _doc for the 7.x -> 8.x upgrade.

image

Test data:
https://drive.google.com/file/d/1DNdzUgeNwsWKaDwaWQOiOzEwibouqov3/view?usp=sharing

@joshdover joshdover added Team:Operations Team label for Operations Team v7.0.0 v7.2.0 labels Feb 26, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations

@joshdover joshdover changed the title Add reindex warning for mapping type changes [UA] Add reindex warning for mapping type changes Feb 26, 2019
@@ -173,37 +173,6 @@ export class WarningsFlyoutStep extends React.Component<
documentationUrl="https://www.elastic.co/guide/en/apm/get-started/master/apm-release-notes.html"
/>
)}

{warnings.includes(ReindexWarning.booleanFields) && (
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Doesn't apply to 7.0 so I removed this and the allField warnings.

@joshdover
Copy link
Contributor Author

@gchaps Do you have any feedback on the copy here? For reference, here are the other warnings we've added in prior versions:

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@gchaps
Copy link
Contributor

gchaps commented Feb 27, 2019

@joshdover Can we use the same text as in the first warning on the page:

This index requires destructive changes that can't be undone

Back up your index, then proceed with the reindex by accepting each breaking change.

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Copy link
Contributor

@tylersmalley tylersmalley left a comment

Choose a reason for hiding this comment

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

LGTM, tested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants