update coerce and breaking changes documentation
This commit is contained in:
parent
61f39e6c92
commit
55635d5de1
|
@ -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:
|
||||
|
||||
|
|
|
@ -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 <<geo-point, geo_point>> field mapping.
|
||||
|
||||
[float]
|
||||
=== Scripting and security
|
||||
|
||||
|
|
Loading…
Reference in New Issue