Upgrade assistant|reindex: Prompt to remove include_in_all in addition to _all #41213
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Upgrade Assistant
Team:Kibana Management
Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
5.6 -> 6.8
It looks like there is a bug (miss) introduced as part of #27457.
In 27457, we added an automatic index changes feature as part of the reindexing functionality. For 6.7.0, these are limited to these 2 items below:
However, item 1 above is not sufficient depending on the use case.
To reproduce:
include_in_all
:Upgrade to 6.7 (reproducible in both 6.7.0 and 6.8.1)
Launch the upgrade assistant:
It will detect that this index was created in 5.x and requires reindexing. If you proceed to reindex, it will ask for the confirmation to perform the automatic index change as part of reindexing (i.e., removal of the _all field).
include_in_all
option still intact (so it is rejected by Elasticsearch 6.7):If you look at the mapping included in Kibana's rest API exception above, you will see that the
/reindexed-v6-logstash-ams_metrics-2017.08.15_2
index it tries to create is using a mapping that has the_all
successfully removed, however,include_in_all
is present so it is causing Elasticsearch to reject this new index.Users with _all and include_in_all will likely have to workaround this by calling the ES reindex API directly outside of the upgrade assistant UI to perform the reindexing (after creating a target index mapping that is valid in 6.x first).
The text was updated successfully, but these errors were encountered: