mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 09:48:58 -04:00
[GIS] Updates mapping to reflect that in ES (#28038)
On start-up, Kibana migrations check the mappings of the Kibana index to determine if there are differing mappings, if so, we re-index the data. When setting `"tree": "quadtree"`, ES is actually representing it in the mapping as `"strategy": "recursive"`. This causes the migrations to always run. These are both defaults for the geo_shape data type, so there shouldn't be any adverse effect here. Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
This commit is contained in:
parent
61fcf98b6e
commit
45dfd5046d
1 changed files with 1 additions and 2 deletions
|
@ -11,8 +11,7 @@
|
|||
"type": "integer"
|
||||
},
|
||||
"bounds": {
|
||||
"type": "geo_shape",
|
||||
"tree": "quadtree"
|
||||
"type": "geo_shape"
|
||||
},
|
||||
"mapStateJSON": {
|
||||
"type": "text"
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue