Ideas
Give us your best ideas!
Give us your best ideas!
Give us your best ideas!
It would be great if the platform itself noticed when changes demands an incrementation of the Elistic search index prefix.
As this is a manual operation for the development team, this should be automated with decrease risk of failing deploys to test and production.
Ludvig Bergander
We regard this as shipped, considering the solution implemented in 8.5 described in the previous comment.
Hi,
In 8.5 we introduced maintenance of index schemas including offline rebuilds. Read more about this.
In this work, we were considering automatic re-indexing at start up if the schema did not match. However we decided not to introduce this since it might trigger unwished indexing in multi server environments.
Are you mostly experiencing this as an issue in projects running older versions than 8.5?