da6b61e8ef
Currently, if geo context is represented by something other than geo_point or an object with lat and lon fields, the parsing of it as a geo context can result in ignoring the context altogether, returning confusing errors such as number_format_exception or trying to parse the number specifying as long-encoded hash code. It would also fail if the geo_point was stored. This commit makes the mapping parsing more strict and will fail during mapping update or index creation if the geo context doesn't point to a geo_point field. Supersedes #32412 Closes #32202 |
||
|---|---|---|
| .. | ||
| aggregations.asciidoc | ||
| analysis.asciidoc | ||
| api.asciidoc | ||
| cluster.asciidoc | ||
| indices.asciidoc | ||
| java.asciidoc | ||
| mappings.asciidoc | ||
| packaging.asciidoc | ||
| plugins.asciidoc | ||
| restclient.asciidoc | ||
| scripting.asciidoc | ||
| search.asciidoc | ||
| settings.asciidoc | ||
| snapshotstats.asciidoc | ||