This overhaul of the docs structure puts Kibana's documentation more
inline with the structure that is used in Elasticsearch. This will help
us better organize the docs going forward as more docs are added.
This also includes a few necessary content changes for 5.0.
Since we introduced the ability for users to manually manipulate some of
the JSON used in Elasticsearch requests in the form of of the filter
editor in 4.3, it's possible that saved objects are taking advantage of
then-deprecated and now-removed Elasticsearch functionality.
This calls out that possibility and links to the Elasticsearch breaking
changes documentation for more information. Even though this is
technically not a Kibana BC break, it manifests as if it were an issue
with Kibana since it results in broken
searches/visualizations/dashboards.
Fixes#8511
---------
**Commit 1:**
Align better with ES doc structure
* Original sha: 48c3da71b9
* Authored by Matthew Bargar <mbargar@gmail.com> on 2016-10-18T22:22:53Z
**Commit 2:**
Improve formatting and details of breaking changes docs
* Original sha: 4a59a7c93c
* Authored by Matthew Bargar <mbargar@gmail.com> on 2016-10-19T16:55:06Z
---------
**Commit 1:**
[server/logging] intercept ECONNRESET messages and downgrade them
* Original sha: 38bcad9a05
* Authored by spalger <email@spalger.com> on 2016-10-20T19:24:16Z
**Commit 2:**
[server/logging] remove doTagsMatch() helper
* Original sha: a8eea585d5
* Authored by spalger <email@spalger.com> on 2016-10-20T20:19:33Z
**Commit 3:**
[server/logging] add tests for log interceptor
* Original sha: 866abcc820
* Authored by spalger <email@spalger.com> on 2016-10-20T20:35:35Z
**Commit 4:**
[server/logging] only match tags that are in the right order
* Original sha: 1973ed8a91
* Authored by spalger <email@spalger.com> on 2016-10-20T20:50:26Z
**Commit 5:**
[server/logging] remove unused dependency
* Original sha: dbe5f6fb72
* Authored by spalger <email@spalger.com> on 2016-10-20T20:58:59Z
**Commit 6:**
[server/logging] fix the order we expect tags to be in
* Original sha: 76e09e6740
* Authored by spalger <email@spalger.com> on 2016-10-20T21:04:58Z
---------
**Commit 1:**
[timelion] Remove saved sheets link
Currently saved timelion sheets are not showing up in the saved objects page, so the link errors and loads a blank page
* Original sha: 19e5af9f6e
* Authored by Jonathan Budzenski <jon@jbudz.me> on 2016-10-20T14:29:15Z
---------
**Commit 1:**
Disabling the uiSettings for the cli_plugin install
* Original sha: 81ff2eb639
* Authored by = <brandon.kobel@elastic.co> on 2016-10-20T14:18:17Z
---------
**Commit 1:**
UI Settings disabled when plugins.initialize is false
* Original sha: c6f90e2fd3
* Authored by = <brandon.kobel@elastic.co> on 2016-10-19T20:47:05Z
**Commit 2:**
Moving where we're disabling the ui settings
* Original sha: e66c7e79f9
* Authored by = <brandon.kobel@elastic.co> on 2016-10-19T21:22:52Z
**Commit 3:**
[server/uiSettings] add enabled config
in response to matt's comment that relying on `plugins.initialize` is kinda dirty (with which we all agree) we're adding an undocumented config value that the dev cli can use to put prevent the optimizr server from logging meaningless warnings
* Original sha: 40ffd12238
* Authored by spalger <email@spalger.com> on 2016-10-19T23:24:55Z
**Commit 4:**
[server/uiSettings] react to missing elasticsearch plugin
* Original sha: 7feacf6a70
* Authored by spalger <email@spalger.com> on 2016-10-19T23:26:44Z
**Commit 5:**
[server/uiSettings] fix da tests
* Original sha: c2d7d0136a
* Authored by spalger <email@spalger.com> on 2016-10-19T23:36:11Z
**Commit 6:**
[server/uiSettings] document enabled config
* Original sha: f9bd154fcd
* Authored by Spencer <spalger@users.noreply.github.com> on 2016-10-19T23:52:28Z
* Committed by GitHub <noreply@github.com> on 2016-10-19T23:52:28Z
---------
**Commit 1:**
URI-encode forwarded location header in proxy
Right now there are situations in which ElasticSearch puts characters in
the character code range between 128 and 255 into the `Location` header.
This leads to an exception when trying to pass on that header through
the hapi proxy in versions before 15.0.0, because it validates that only
US-ASCII characters are used in headers.
To work around that situation, the `Location` header is encoded using
`encodeURI()` for now.
Closes#8705
* Original sha: 18c23c17d9
* Authored by Felix Stürmer <stuermer@weltenwort.de> on 2016-10-18T17:55:31Z
**Commit 2:**
Add test to verify umlaut in vis name
Relates to #8705
* Original sha: e100e1f5c9
* Authored by Felix Stürmer <stuermer@weltenwort.de> on 2016-10-19T09:01:46Z
**Commit 3:**
[elasticsearch/proxy] use different code path with erorr
* Original sha: fec5e1a2dc
* Authored by spalger <email@spalger.com> on 2016-10-19T19:06:39Z
---------
**Commit 1:**
Generate key for ip range from/to agg
Elasticsearch 5.0 no longer returns a `key` prop with ip range buckets
when from/to is used in the request. Looking at the [2.x docs][1] it
appears to be a mistake that it was ever included in the first place.
So now we'll generate the key ourselves.
[1]: https://www.elastic.co/guide/en/elasticsearch/reference/2.4/search-aggregations-bucket-iprange-aggregation.html
Fixes: https://github.com/elastic/kibana/issues/8736
* Original sha: f344a4b262
* Authored by Matthew Bargar <mbargar@gmail.com> on 2016-10-18T22:51:56Z
**Commit 2:**
Stop sending null in ip range from/to props
The IP range agg supports open ended ranges. Elasticsearch 2.x was
lenient and accepted null as a value for the from/to props, but the
correct way to do an open ended range was always to omit the from/to
key entirely. ES 5.0 appears to be more strict and barfs when null is
passed. This commit removes the null values.
Fixes https://github.com/elastic/kibana/issues/8741
* Original sha: 3ca45ba546
* Authored by Matthew Bargar <mbargar@gmail.com> on 2016-10-18T23:18:14Z
**Commit 3:**
ip range label and filter improvements
* updated the filter labels to match the range labels
* fixed the filter creation to work for unbound ranges
* Original sha: b153ea0da3
* Authored by Spencer <spalger@users.noreply.github.com> on 2016-10-19T17:57:58Z
* Committed by Matthew Bargar <mbargar@gmail.com> on 2016-10-19T18:36:22Z
---------
**Commit 1:**
Printing process warning's via the appropriate logger
* Original sha: 96ef75b980
* Authored by = <brandon.kobel@elastic.co> on 2016-10-19T10:41:45Z
---------
**Commit 1:**
Conditionally show Visualize button based on aggregatable status
* Original sha: 76c2687e86
* Authored by Matthew Bargar <mbargar@gmail.com> on 2016-10-14T22:23:37Z
**Commit 2:**
Switch to ng-show so controller can maintain reference to Visualize button and remove it upon toggle
* Original sha: 9da6ddfd16
* Authored by Matthew Bargar <mbargar@gmail.com> on 2016-10-17T17:21:11Z
**Commit 3:**
Add visualizable flag to field object
* Original sha: 75a2f2356d
* Authored by Matthew Bargar <mbargar@gmail.com> on 2016-10-17T17:39:13Z
---------
**Commit 1:**
Ensure boolean scripted field values are of boolean type
they come back from the server as ‘true’ currently. Hopefully that
will be fixed in the future, so to future-proof this I am only
converting when the value is not of type boolean.
Fixes#8677
Need to convert both number and bool strings to their respective types.
Throw an error for unexpected types/values.
* Original sha: 7b8ff74513
* Authored by Stacey Gammon <gammon@elastic.co> on 2016-10-14T19:50:23Z
---------
**Commit 1:**
[npm] update chromedriver
The latest macOS version of Chrome is incompatible with the version of chromedriver we currently depend on, so this updates it.
* Original sha: 29eeed22e2
* Authored by spalger <email@spalger.com> on 2016-10-14T21:03:23Z
---------
**Commit 1:**
Fix our request to ES for filtering on scripted fields
Need to use params.value instead of value.
Fixes#8404
Add params prefix in another spot for painless scripted fields
Fix date histogram with scripted fields
Remove format: epoch_millis so the script compiles. I am not 100%
confident of the side affect from this (it’s used for non-scripted
fields, but I’m not sure where I would put it for scripted fields, or
if it’s needed). At any rate, it appears that formatting settings for
scripted fields is still being honored, even after removing it from
params.
* Original sha: 7cdb74d6c9
* Authored by Stacey Gammon <gammon@elastic.co> on 2016-10-12T14:54:23Z
---------
**Commit 1:**
[agg_response/point_series] always assign series labels to points
Since forever, the vislib has been compensating for a behavior/bug in the agg_response module where "series" labels were not assigned to points if there wasn't a "series" aggregation or multiple y-axis. To compensate for this, the vislib was assigning the yAxisLabel to the series, which had the same effect, but now that the legend is rendered in it's own tick, followed by the visualization, and that behavior was being executed during the vislib render, the legend has been flashing an empty row for a while (this was worsened by the fact that vislib rendering did not trigger a digest cycle).
These changes remove the workaround code from the vislib, and update the agg_response to always send the y-axis label as the series label when there is no series aggregation. Behavior with multiple-y-axis and multiple series aggs should be preserved.
* Original sha: 7460c0ac2d
* Authored by spalger <email@spalger.com> on 2016-10-04T18:40:41Z
**Commit 2:**
[agg_response/point_series] update tests to reflect changes in 19773a6
* Original sha: f681d6cf86
* Authored by spalger <email@spalger.com> on 2016-10-04T19:22:55Z
**Commit 3:**
[agg_response/point_series] apply PR feedback
* Original sha: a119577af8
* Authored by spalger <email@spalger.com> on 2016-10-04T20:41:29Z
**Commit 4:**
[agg_response/point_series] use no-digest promises in tests
* Original sha: 8d370826c4
* Authored by spalger <email@spalger.com> on 2016-10-04T20:45:02Z
---------
**Commit 1:**
typo fix for advanced-settings.asciidoc
* Original sha: 45a1e5b8f8
* Authored by fanfan <yu.qifan@zte.com.cn> on 2016-10-13T02:08:25Z
