31 lines
1.3 KiB
Text
31 lines
1.3 KiB
Text
[[breaking-changes-6.0]]
|
|
== Breaking changes in 6.0
|
|
|
|
This section discusses the changes that you need to be aware of when migrating
|
|
your application to Kibana 6.0.
|
|
|
|
[float]
|
|
=== Removed option to use unsupported scripting languages
|
|
*Details:* Kibana 5.x allowed users to create scripted fields using any scripting language enabled in Elasticsearch.
|
|
Kibana 6.0 will only support Painless and Lucene expression based scripts.
|
|
|
|
|
|
*Impact:* You will need to migrate your groovy, python, javascript, etc. scripted fields to Painless or Lucene expressions.
|
|
|
|
[float]
|
|
=== Changed response format of status API
|
|
*Details:* In an effort to align with our style guidelines and provide a digestible response,
|
|
the status API has changed:
|
|
|
|
* Properties are now snake cased and several have been renamed
|
|
* Metrics now provide the latest available data instead of samples over time
|
|
|
|
*Impact:* You will need to update anything using the status API and expecting the previous response format.
|
|
|
|
[float]
|
|
=== Timelion requires comma to separate queries
|
|
*Details:* Kibana 5.x allowed users to use spaces as a query separator in timelion `.es(400) .es(500)`.
|
|
This is no longer the case. Now, only commas are a valid query separator: e.g. `.es(400), .es(500)`
|
|
|
|
|
|
*Impact:* You will need to migrate your stored timelion queries to the new syntax.
|