[DOCS]Adds breaking change for index patterns (#35318)

* add index breaking change

* add migrate info

* pr feedback

* pr feedback

* move index pattern change to 7.1

* fix version number
This commit is contained in:
Sarah Hersh 2019-04-30 17:06:12 -04:00 committed by GitHub
parent 6c6930cad7
commit f49fa3288f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 22 additions and 2 deletions

View file

@ -6,8 +6,8 @@
This section discusses the changes that you need to be aware of when migrating
your application from one version of Kibana to another.
* <<breaking-changes-7.0,Breaking changes in 7.1>>
* <<breaking-changes-7.0,Breaking changes in 7.0>>
* <<breaking-changes-7.1, Breaking changes in 7.1>>
* <<breaking-changes-7.0, Breaking changes in 7.0>>
See also <<release-highlights>> and <<release-notes>>.
--

View file

@ -11,6 +11,26 @@ See also <<release-highlights>> and <<release-notes>>.
coming[7.1.0]
* <<breaking_71_index_pattern_changes>>
[float]
[[breaking_71_index_pattern_changes]]
=== Index pattern changes
[float]
==== Time-based internal index patterns queried as wildcard index patterns
*Details:* Time-based interval index patterns were deprecated in 5.x. In 6.x,
you could no longer create time-based interval index patterns, but they continued
to function as expected. In 7.1, functionality has changed such that {kib} will
automatically query a time-based interval index pattern as a wildcard index pattern.
Support for time-based index patterns will be removed in 8.0. You can migrate your
time-based index patterns to a wildcard pattern to prepare for this change.
*Impact:* If you query a time-based index pattern, that query will now be performed
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-*`.
//NOTE: The notable-breaking-changes tagged regions are re-used in the
//Installation and Upgrade Guide