github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-23 17:28:26 -04:00
Code Issues Projects Releases Packages Wiki Activity

docs: removal of "expand indices" feature in breaking changes (#12830)

Browse source 
* docs: removal of "expand indices" feature in breaking changes

* docs: remove "expand indices" from index pattern

This feature no longer exists.
This commit is contained in:
Court Ewing 2017-07-13 09:46:29 -04:00 • committed by GitHub
parent 807e572927
commit 748d604fd4
2 changed files with 7 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/management/index-patterns.asciidoc
View file

@ -35,9 +35,6 @@ list.
contains time-based events* option and select the index field that contains the timestamp. Kibana reads the index
mapping to list all of the fields that contain a timestamp.
. By default, Kibana restricts wildcard expansion of time-based index patterns to indices with data within the currently
selected time range. Click *Do not expand index pattern when search* to disable this behavior.
. Click *Create* to add the index pattern.
. To designate the new pattern as the default pattern to load when you view the Discover tab, click the *favorite*

7
docs/migration/migrate_6_0.asciidoc
View file

@ -65,3 +65,10 @@ This is no longer the case. Now, only commas are a valid query separator: e.g. `
*Details:* Kibana 5.x redirected requests from http to https on the same port if TLS was configured. Starting in Kibana 6.0.0, Kibana no longer redirects basic http traffic to https.
*Impact:* With the new configuration setting `server.ssl.redirectHttpFromPort` you can specify a port that will redirect from http to https. This cannot be the same port as the https port.
[float]
=== Removed "expand index pattern when searching" setting for index patterns
*Details:* Since 4.3, index patterns could be configured to do a pre-flight field_stats request before a search in order to determine exact indices that could contain matching documents. Elasticsearch now optimizes searches internally in a similar way and has also removed the field_stats API, so this option was removed from Kibana entirely.
*Impact:* No change is required for existing Kibana index patterns. Those previously configured with this option will gracefully use the new Elasticsearch optimizations instead, as will all new index patterns.