[docs] Enforce a single type for migrated Kibana index (#14884)

This prevents users from using tools which insert dashboards/visualizations directly into the index, which would cause Kibana to stop functioning.

Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
This commit is contained in:
Tyler Smalley 2017-11-13 14:39:44 -08:00 committed by Tyler Smalley
parent dc091b36c1
commit 159ad4d2f2

View file

@ -10,7 +10,7 @@ In order to migrate to Kibana 6, your Kibana index needs to be reindexed. This w
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.
NOTE: To perform this migration without downtime, you will need to be running Kibana 5.6. This is the only version which supports both of the index types. If you are running a version prior to 5.6, you will need to remove `index.format` from the second step.
NOTE: To perform this migration without downtime, you will need to be running Kibana 5.6. This is the only version which supports both of the index types. If you are running a version prior to 5.6, you will need to omit `index.format` and `index.mapping.single_type` from the second step.
. Set `.kibana` index to read-only:
+
@ -35,7 +35,8 @@ PUT .kibana-6
"settings" : {
"number_of_shards" : 1,
"index.format": 6,
"index.mapper.dynamic": false
"index.mapper.dynamic": false,
"index.mapping.single_type": true
},
"mappings" : {
"doc": {