Elasticsearch support

It’s not an issue, but more like an initial investigation: do you have any Elasticsearch support in your future plans? If yes - I’m interested to learn more about it. If no - was it ever considered before and deliberately rejected or else?

It is true, that Elasticsearch is somewhat different in matter of ‘schema’ management, since it has a dynamic mappings allowed by default and as such it looks like not a relevant candidate for migration tools.

Yet, there are few use-cases where i can see Flyway being relevant for ES management:

• some of organizations (like mine current one) prefer to stick to "dynamic":"strict" index/mappings definition, in this case mappings changes are required on each ‘schema’ change and it is better to have it managed/versioned in right way
• data migration/transformation - reindex in ES terms - is a valid case and this one is also requires some kind of management/versioning

[axelfontaine]

No demand so far.

[kpei]

Hi Axel,

We have been enjoying Flyway for a long time now, both private and professionally; so thanks for that 😉

At work had a use case we wanted to manage DDL changes to ElasticSearch also, and since we were already using Flyway for PostgreSQL, I looked into customizing Flyway to also support non-sql migrations. I have managed to do it for both the migration system and the history table. We have enjoyed the simplicity of the sql-files which with proper naming does the migration automatically. I wanted to use the same solution for elastic search, since that was a similar structure to the DDL change statements as well. I also did a small PoC to prove that the history table could be done in-memory directly, or through the use of the in-memory db “H2”.

Below a screenshot of the project; should you be interested in more detail, I would be happy show you some code.

https://snag.gy/iGtJsl.jpg

Cheerz!

Chris

Hi Chris. Anyway to get in touch to talk more about flyway integration with elasticsearch?