453217fd7a
If a user explicitly defined the tree_level or precision parameter in a geo_shape mapping their specification was always overridden by the default_error_pct parameter (even though our docs say this parameter is a 'hint'). This lead to unexpected accuracy problems in the results of a geo_shape filter. (example provided in issue #9691) This simple patch fixes the unexpected behavior by setting the default distance_error_pct parameter to zero when the tree_level or precision parameters are provided by the user. Under the covers the quadtree will now use the tree level defined by the user. The docs will be updated to alert the user to exercise caution with these parameters. Specifying a precision of "1m" for an index using large complex shapes can quickly lead to OOM issues. closes #9691 |
||
|---|---|---|
| .. | ||
| fields | ||
| types | ||
| conf-mappings.asciidoc | ||
| date-format.asciidoc | ||
| dynamic-mapping.asciidoc | ||
| fields.asciidoc | ||
| meta.asciidoc | ||
| transform.asciidoc | ||
| types.asciidoc | ||