Flyway升级4.2.0->5.0.0迁移失败，即使指定flyway.table

Question

我正在更新我们应用程序中落后的一些maven依赖项，从flyway maven插件4.2.0升级时遇到了一个问题，我们的reset和migrate make命令失败了，我找不到任何有用的结果。

最初，我试图从4.2.0转移到5.2.4。当我无法解决我的错误时，我退回到5.0.0的单个版本。在5.0.0的发行说明之后，我将flyway.table=schema_version添加到我的flyway-$env.properties文件中，并更新了我的Makefile命令以使用-Dflyway.configFiles=

当我尝试迁移现有数据库飞行路线时，会尝试应用所有脚本，从而导致初始数据库脚本出现约束冲突。尝试迁移空数据库飞行通道时，如果在运行初始脚本后无法锁定schema_version表，则失败。

make命令执行以下操作:

@mvn -pl db flyway:repair \
    -Dflyway.url="jdbc:mysql://${FLYWAY_TARGET_HOST}:${FLYWAY_TARGET_PORT}/${FLYWAY_TARGET_DB}?useUnicode=true&characterEncoding=utf8&useSSL=false" \
    -Dflyway.password=${FLYWAY_TARGET_DB_PW} \
    -Dflyway.user=${FLYWAY_TARGET_DB_USER} \
    -Dflyway.configFiles="src/main/resources/config/flyway/${FLYWAY_CONFIG_FILENAME}.properties"
@mvn -pl db flyway:migrate \
    -Dflyway.url="jdbc:mysql://${FLYWAY_TARGET_HOST}:${FLYWAY_TARGET_PORT}/${FLYWAY_TARGET_DB}?useUnicode=true&characterEncoding=utf8&useSSL=false" \
    -Dflyway.password=${FLYWAY_TARGET_DB_PW} \
    -Dflyway.user=${FLYWAY_TARGET_DB_USER} \
    -Dflyway.configFiles="src/main/resources/config/flyway/${FLYWAY_CONFIG_FILENAME}.properties"

在空数据库上运行时，会提供以下输出:

[INFO] --- flyway-maven-plugin:5.0.0:migrate (default-cli) @ db ---
[INFO] Flyway Community Edition 5.0.0 by Boxfuse
[INFO] Database: jdbc:mysql://localhost:3306/db_test (MySQL 5.7)
[INFO] Successfully validated 46 migrations (execution time 00:00.029s)
[INFO] Creating Schema History table: `db_test`.`schema_version`
[WARNING] Could not find schema history table `db_test`.`schema_version`, but found `db_test`.`schema_version` instead. You are seeing this message because Flyway changed its default for flyway.table in version 5.0.0 to flyway_schema_history and you are still relying on the old default (schema_version). Set flyway.table=schema_version in your configuration to fix this. This fallback mechanism will be removed in Flyway 6.0.0.
[INFO] Current version of schema `db_test`: << Empty Schema >>
[INFO] Migrating schema `db_test` to version 1.0 - DbBaseline
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.799 s
[INFO] Finished at: 2019-04-23T18:12:57-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.flywaydb:flyway-maven-plugin:5.0.0:migrate (default-cli) on project db: org.flywaydb.core.internal.exception.FlywaySqlException: 
[ERROR] Unable to lock table `db_test`.`schema_version`

Answer 1

在清醒地看待这一点之后，问题在于我们的 V1.0 脚本，特别是我们在创建表之前删除并重新创建架构。这导致在应用 V1.0 脚本后，飞行方式生成的表不存在。

删除这一行后，所有flyway作业都会正确执行。幸运的是，flyway:repair纠正了< code>schema_version表中的校验和，无需任何修改或手动编辑数据库。