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

[7.2] Add PR #31739 to 7.2 migration doc #38740

Merged
merged 1 commit into from
Jun 12, 2019
Merged

[7.2] Add PR #31739 to 7.2 migration doc #38740

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/migration/migrate_7_2.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ coming[7.2.0]


* <<breaking_72_index_pattern_changes>>
* <<breaking_72_saved_objects_migration_changes>>


[float]
Expand All @@ -32,6 +33,17 @@ time-based index patterns to a wildcard pattern to prepare for this change.
on the root wildcard term. For example, a query on an index pattern such as
`[logstash-]YYYY.MM.DD` will now query all indices that match `logstash-*`.

[float]
[[breaking_72_saved_objects_migration_changes]]
=== Saved object migration changes

[float]
==== New error is thrown when a plugin defines a migration for a mapping it doesn't define or own
*Details:* Kibana will now throw an error on startup if a plugin has defined
a saved object migration inside a plugin that doesn't define or own the mappings to.

*Impact:* If you define migrations within your plugin but the mappings is
owned by another plugin, Kibana will no longer allow that and not start up.

//NOTE: The notable-breaking-changes tagged regions are re-used in the
//Installation and Upgrade Guide
Expand Down