All geek questions in one place

How do I manage the migration / evolution of a schema / evolution in Elasticsearch?

Flyway is a very convenient scheme migration / evolution tool in the RDBMS world. I am looking for something similar for ES.

Even though the ES is different from the DBMS, and I understand that the whole point of a tool like Flyway, basically makes the same circuit changes in several environments , for example, in 5 development environments and intermediate / production environments, Even if I will move on to the approach with the alias described in the blog post , I still need to do this by creating the new-index-then-load -into-it-then-update-alias data in each environment. What I'm looking for is an automatic way to do this.

I can't just ask each developer to run a specific script after he pulls out a specific commit. I also do not want to forget to manually run such scripts in intermediate and production environments after deploying the latest codebase. Especially when the person performing the deployment is not the one who wrote the migration scripts. Everything feels that way 20 years ago.

The problem has been resolved several times in the RDBMS world. There are several mature tools. The flyway is just one of them and my favorite. But I can not find anything like this for ES. I searched half the web for this. Either my Google playing skills are very poor, or such a tool does not exist.

What am I missing? Is there a tool that I cannot find? Or am I completely misunderstanding something about ES, and such a tool does not make sense because of something I don’t understand yet?

+6
source share
1 answer

In create-new-index-then-load-data-into-it-then-update-aliaswe do the following:

  • We use templates to display
  • And we use curator to automatically create / update index / alias.

However, the curator should be run periodically, but we run it in the cron job.

+6
source

Source: https://habr.com/ru/post/1016497/

More articles:


All Articles