Large migrations stored in S3 are downloaded, even when they aren't run.

[OneGeek]

Which version and edition of Flyway are you using?

9.22.3 Community

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)

Maven plugin (9.21.1)

Which database are you using? (Type & version)

MariaDB 10.6

Which operating system are you using?

Windows (10/11) & Linux (Amazon Linux 2)

What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)

I have a 1.3GB migration stored in S3. I ran flyway repair & flyway migrate against an empty DB, and against a DB where flyway migrate has already been run.

What did you expect to see?

In the case where the DB is empty, I expect the large migration to not be downloaded when running flyway repair, and then to be downloaded once from S3, then applied, when running flyway migrate

In the case where the DB is populated, and the large migration has already run, I expect flyway to not download the migration at all for either repair or migrate operations.

What did you see instead?

In the case where the DB is empty, the migration is downloaded multiple times. Once when running repair and once when running migrate.

In the case where the DB is populated, the migration is downloaded despite already having been run.

In both cases, due to the size of the migration file, multiple minutes are spent redownloading the file when it doesn't seem like it should be necessary to do so if the migration isn't going to run.

[mauroEkotrope]

Hoping this issue gets resolved soon; it just cost me 45 minutes!

[giacomoarru]

I have the same issue. S3 migrations are broken and they cannot be used for any real project, since it takes forever to run the software. Migrations should be downloaded only if necessary.