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: fix erroneous references to es-ref

Browse source
This commit is contained in:
Court Ewing 2017-11-13 20:26:32 -05:00
parent 3e1cf3d0ba
commit 07a6c026f1
3 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/migration/migrate_6_0.asciidoc
View file

@ -6,13 +6,13 @@ your application to Kibana 6.0.
[float]
=== Types removed from Kibana index
*Details:*
With the imminent {es-ref}/removal-of-types.html[removal of types in Elasticsearch], we have updated our index to not rely on types. Kibana 5.6.x can support both of these mappings to minimize downtime. A new UI is provided with X-Pack to assist with the migration of the Elastic stack.
*Details:*
With the imminent {ref}/removal-of-types.html[removal of types in Elasticsearch], we have updated our index to not rely on types. Kibana 5.6.x can support both of these mappings to minimize downtime. A new UI is provided with X-Pack to assist with the migration of the Elastic stack.
*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 include only a single `_type`. If you have multiple different values for _type in a single index, we recommend to move `_type` to another field or separate the different types of documents into different indices. 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 include only a single `_type`. If you have multiple different values for _type in a single index, we recommend to move `_type` to another field or separate the different types of documents into different indices. 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

2
docs/migration/migrate_6_0_index.asciidoc
View file

@ -6,7 +6,7 @@
The following will make transformations to your Kibana index. It is recommended you https://www.elastic.co/guide/en/elasticsearch/reference/5.6/modules-snapshots.html[backup your Kibana index] prior to running any of the following commands.
==============================================
In order to migrate to Kibana 6, your Kibana index needs to be reindexed. This will make transformations to the data model, removing types which are being {es-ref}/removal-of-types.html[removed in Elasticsearch].
In order to migrate to Kibana 6, your Kibana index needs to be reindexed. This will make transformations to the data model, removing types which are being {ref}/removal-of-types.html[removed in Elasticsearch].
A UI is available in X-Pack 5.6 to assist with the migration. The following is provided should you be required to run the migration manually. The commands assume you're using the default `.kibana` index, without an alias. If `kibana.index` is set to something different in your `kibana.yml`, or you're using an alias, you will need to modify the commands.

2
docs/visualize/tilemap.asciidoc
View file

@ -33,7 +33,7 @@ Enter a string in the *Custom Label* field to change the display label.
===== Buckets
Coordinate maps use the {es-ref}search-aggregations-bucket-geohashgrid-aggregation.html[_geohash_] aggregation. Select a field, typically coordinates, from the
Coordinate maps use the {ref}search-aggregations-bucket-geohashgrid-aggregation.html[_geohash_] aggregation. Select a field, typically coordinates, from the
drop-down.
- The_Change precision on map zoom_ box is checked by default. Uncheck the box to disable this behavior.