docs: Note deprecated ES features in breaking changes

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
This commit is contained in:
Court Ewing 2016-10-23 17:13:38 -04:00
parent 897b296762
commit e5f5263339

View file

@ -51,3 +51,16 @@ to the dashboard's metadata, which you can persist by saving the dashboard.
*Impact:* This change will not affect the functionality of the dashboard itself,
but you must save the dashboard before using certain features such as X-Pack reporting.
==== Saved objects with previously deprecated Elasticsearch features
*Details:* Since Kibana 4.3, users have been able to arbitrarily modify filters
via a generic JSON editor. If users took advantage of any deprecated Elasticsearch
features in this way, then they will cause errors in Kibana since they're removed
from Elasticsearch 5.0. Check the Elasticsearch
{ref}/breaking_50_search_changes.html#_deprecated_queries_removed[breaking changes]
documentation for more details.
*Impact*: Discover, Visualize, and Dashboard will error for any saved objects that
are relying on removed Elasticsearch functionality. Users will need to update the
JSON of any affected filters.