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

Update migrate_6_0.asciidoc (#14842)

Browse source 
Adding additional type example
This commit is contained in:
Alex F 2017-11-08 08:05:12 -05:00 • committed by GitHub
parent 0af05715b2
commit e532324e47
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/migration/migrate_6_0.asciidoc
View file

@ -10,7 +10,7 @@ your application to Kibana 6.0.
*Impact:*
* Types have been removed from the `.kibana` index. You will need migrate your Kibana index either {kibana-ref}/migrating-6.0-index.html[manually], or through the Upgrade Assistant in X-Pack.
* Upon upgrade of a typical deployment with indices created on a regular basis (e.g. coming from Logstash) to 6.0, new indices will have to not include `_type`. If the information encoded in `_type` is valuable, we recommend to move it to another field. Any dashboards relying on filtering and aggregating on `_type` will continue to work, but will not show any meaningful data. Users will need to update dashboards to rely on aggregating and filtering on the new field, instead of `_type`, if they want to leverage that information going forward.
* Upon upgrade of a typical deployment with indices created on a regular basis (e.g. coming from Logstash) to 6.0, new indices will have to not include `_type`. If the information encoded in `_type` is valuable, we recommend to move it to another field. Any dashboards relying on filtering and aggregating on `_type` will continue to work, but will not show any meaningful data. Users will need to update dashboards to rely on aggregating and filtering on the new field, instead of `_type`, if they want to leverage that information going forward.
[float]
=== Removed option to use unsupported scripting languages