Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rollback / down migrations #706

Open
heyarne opened this issue Nov 3, 2022 · 5 comments
Open

Rollback / down migrations #706

heyarne opened this issue Nov 3, 2022 · 5 comments

Comments

@heyarne
Copy link

heyarne commented Nov 3, 2022

Hi! I didn't find any information on how to undo migrations, am I missing something or is it currently unsupported? And if they are currently unsupported, are there any plans to change this?

@michael-simons
Copy link
Owner

That’s correct, it isn’t there yet.

I won’t go down a fully automated route (maybe apart from the the catalog based approach, there I know the opposite operations), but the same approach like Flyway (you’ll need to provide an undo migration with the reverse op) as cypher too and than we manage the rest.

I’ll keep this here as new feature request.

In general, thanks a lot for your interest!

@heyarne
Copy link
Author

heyarne commented Nov 3, 2022

Thank you for the quick response! This tool has already been quite helpful to me as is. I'm using Cypher-migrations personally, and providing a $migration-name.down.cypher next to the original migration would 100% work for me.

@michael-simons
Copy link
Owner

Thank you for your kind words, much appreciated.

Current plan is repeatable migrations first, which is nearly done.

Unrelated to that, what is your Java env if I may ask? 8, 11, 17 or newer?

@heyarne
Copy link
Author

heyarne commented Nov 3, 2022

It's java 11 at the moment, but I control the environments so I'm free to update whenever it makes sense.

@michael-simons
Copy link
Owner

Thanks! My plan is going to 17 for 2.0 by the end of the year. Aligned a bit with Spring Boot 3 and most likely Quarkus 3 as well.

I’ll will support 1.13.x or 1.14.x still, but rather not adding bigger things to them.

Don’t know yet how much of an effort undo migrations might be. Proper storing them in our internal subgraph might be the biggest part to do some thinking.

Again, thanks a lot for your input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants