-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Description
Elasticsearch version: 6.3.0
Plugins installed: Vanilla found.io installation
JVM version: Vanilla found.io installation
OS version: Vanilla found.io options
Description of the problem including expected versus actual behavior:
When creating an index with a field of type geo_shape that uses the term strategy, I've observed some strange behaviors (this is in hosted 6.3.0).
Creating an index with a geoshape field set to term strategy takes just over 30 seconds (feeling very much like a timeout), but does ultimately report success. However, if you subsequently try to change any settings, you get a mapper parsing error about the original supposedly successfully created mapping having an unsupported points_only field (whether or not not you explicitly specified it, or just got it from using the term strategy).
Steps to reproduce:
Please include a minimal but complete recreation of the problem, including
(e.g.) index creation, mappings, settings, query etc. The easier you make for
us to reproduce it, the more likely that somebody will take the time to look at it.
- Create mapping
PUT /example
{
"mappings": {
"doc": {
"properties": {
"location": {
"type": "geo_shape",
"tree": "quadtree",
"precision": "10m",
"strategy": "term"
}
}
}
}
}
- Change a setting
PUT /example/_settings
{
"settings": {"refresh_interval": "-1"}
}
Response
{
"error": {
"root_cause": [
{
"type": "mapper_parsing_exception",
"reason": "Mapping definition for [location] has unsupported parameters: [points_only : true]"
}
],
"type": "mapper_parsing_exception",
"reason": "Failed to parse mapping [doc]: Mapping definition for [location] has unsupported parameters: [points_only : true]",
"caused_by": {
"type": "mapper_parsing_exception",
"reason": "Mapping definition for [location] has unsupported parameters: [points_only : true]"
}
},
"status": 400
}