42 lines
No EOL
1.5 KiB
Text
42 lines
No EOL
1.5 KiB
Text
[[breaking-changes-7.2]]
|
|
== Breaking changes in 7.2
|
|
++++
|
|
<titleabbrev>7.2</titleabbrev>
|
|
++++
|
|
|
|
This section discusses the changes that you need to be aware of when migrating
|
|
your application to Kibana 7.2.
|
|
|
|
See also {kibana-ref-all}/7.2/release-highlights-7.2.0.html[release highlights]
|
|
and <<release-notes-7.2.0, release notes>>.
|
|
|
|
//NOTE: The notable-breaking-changes tagged regions are re-used in the
|
|
//Installation and Upgrade Guide
|
|
|
|
//tag::notable-breaking-changes[]
|
|
|
|
// end::notable-breaking-changes[]
|
|
|
|
[float]
|
|
[[breaking_72_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.2, 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
|
|
|
|
//tag::notable-breaking-changes[]
|
|
|
|
// end::notable-breaking-changes[] |