From 55635d5de126e27d68f83e28ac43fba95a172324 Mon Sep 17 00:00:00 2001 From: Nicholas Knize Date: Thu, 3 Dec 2015 09:53:19 -0600 Subject: [PATCH] update coerce and breaking changes documentation --- docs/reference/mapping/params/coerce.asciidoc | 1 - docs/reference/migration/migrate_2_2.asciidoc | 10 ++++++++++ 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/reference/mapping/params/coerce.asciidoc b/docs/reference/mapping/params/coerce.asciidoc index c9491607a6b..0121c307230 100644 --- a/docs/reference/mapping/params/coerce.asciidoc +++ b/docs/reference/mapping/params/coerce.asciidoc @@ -12,7 +12,6 @@ For instance: * Strings will be coerced to numbers. * Floating points will be truncated for integer values. -* Lon/lat geo-points will be normalized to a standard -180:180 / -90:90 coordinate system. For instance: diff --git a/docs/reference/migration/migrate_2_2.asciidoc b/docs/reference/migration/migrate_2_2.asciidoc index 39c059e7f47..9611d86a2ac 100644 --- a/docs/reference/migration/migrate_2_2.asciidoc +++ b/docs/reference/migration/migrate_2_2.asciidoc @@ -4,6 +4,16 @@ This section discusses the changes that you need to be aware of when migrating your application to Elasticsearch 2.2. +[[float]] +=== Mapping APIs + +==== Geo Point Type + +The `geo_point` format has been changed to reduce index size and the time required to both index and query +geo point data. To make these performance improvements possible both `doc_values` are `coerce` are required +and therefore cannot be changed. For this reason the `doc_values` and `coerce` parameters have been removed +from the <> field mapping. + [float] === Scripting and security