From e66f11c758227c28072556dd49e3e20623a06329 Mon Sep 17 00:00:00 2001 From: James Rodewig Date: Wed, 24 Apr 2019 15:38:16 -0400 Subject: [PATCH] [DOCS] Specify ID for index property section to prepare for Asciidoctor migration --- docs/reference/migration/migrate_5_0/mapping.asciidoc | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/reference/migration/migrate_5_0/mapping.asciidoc b/docs/reference/migration/migrate_5_0/mapping.asciidoc index bfe4a4adafbbb..97d065e32ae82 100644 --- a/docs/reference/migration/migrate_5_0/mapping.asciidoc +++ b/docs/reference/migration/migrate_5_0/mapping.asciidoc @@ -93,6 +93,7 @@ current timestamp on application side. For `_ttl`, you should either use time-based indices when applicable, or cron a delete-by-query with a range query on a timestamp field +[[_literal_index_literal_property]] ==== `index` property On all field datatypes (except for the deprecated `string` field), the `index`