Re: Handling migrations if dbScript exists in snapshot?

I sent out a review for a prototype of my proposed migration system here: https://reviews.apache.org/r/45467/ Please take a look at the review and let me know if it seems reasonable at a high level (noting the caveats called out in the review description, this is not production quality code,

Re: Handling migrations if dbScript exists in snapshot?

> > I think in the event that we have to rollback after applying a change like > you describe we'd either have to resort to a manual fix or restore from > backup. I am afraid restoring from backup will not be an acceptable solution if/when a new version has to be rolled back after running for

Re: Handling migrations if dbScript exists in snapshot?

Flyway has a fairly well reasoned response to the downgrades question: https://flywaydb.org/documentation/faq#downgrade I think in the event that we have to rollback after applying a change like you describe we'd either have to resort to a manual fix or restore from backup. The other thing to

Re: Handling migrations if dbScript exists in snapshot?

On Wed, Mar 23, 2016 at 2:21 PM, Joshua Cohen wrote: > Hi Aurorans, > > As you may have seen (https://issues.apache.org/jira/browse/AURORA-1648), > we ran into an issue when upgrading a cluster that uses dbScripts in > snapshots. To restate the problem from the ticket, when