-
Notifications
You must be signed in to change notification settings - Fork 25k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs out of sync regarding default values for geo_shape mapping #23206
Comments
@nknize could you have a look please? |
Hi @clintongormley and @nknize any news on geo search docs being out of date? |
The problem here is not that the docs are out of sync, but that we are showing placeholder values instead of default values in the mapping with |
GeoShapeFieldMapper should show actual defaults instead of placeholder values when the mapping is requested with include_defaults=true. Closes elastic#23206
@imotov thanks for handling this! |
GeoShapeFieldMapper should show actual defaults instead of placeholder values when the mapping is requested with include_defaults=true. Closes #23206
GeoShapeFieldMapper should show actual defaults instead of placeholder values when the mapping is requested with include_defaults=true. Closes #23206
Elasticsearch version: number": "5.1.1", "build_hash": "5395e21" from official Docker image
Description of the problem including expected versus actual behavior:
When I query the default mapping values using mapping API with
?include_defaults=true
I'm getting the following forgeo_shape
field:Above values do not match the default values mentioned in documentation:
https://www.elastic.co/guide/en/elasticsearch/reference/5.1/geo-shape.html#geo-shape-mapping-options
Here's the query result when I've added
precision: 1m
property to geo_shape mapping:Still
tree_levels
is 0 (which is confusing). On the other handdistance_error_pct
changes to 0 as documented.Not sure if it's only docs out o date, because:
tree_levels: 0
seems to be a bugprecision: "-1.0m"
by default does not make senseThe text was updated successfully, but these errors were encountered: