You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Burgess (Jira)" <ji...@apache.org> on 2021/07/16 14:56:00 UTC
[jira] [Updated] (NIFI-8793) Flyway error when upgrading from older
release to 0.8.0
[ https://issues.apache.org/jira/browse/NIFI-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess updated NIFI-8793:
-------------------------------
Component/s: NiFi Registry
> Flyway error when upgrading from older release to 0.8.0
> -------------------------------------------------------
>
> Key: NIFI-8793
> URL: https://issues.apache.org/jira/browse/NIFI-8793
> Project: Apache NiFi
> Issue Type: Bug
> Components: NiFi Registry
> Reporter: Bryan Bende
> Priority: Major
> Fix For: 1.14.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When taking an H2 database from 0.3.0 and dropping it into 0.8.0 or 0.9.0-SNAPSHOT, it produces the following error:
> {code:java}
> Caused by: org.flywaydb.core.api.FlywayException: Found non-empty schema(s) "PUBLIC" without schema history table! Use baseline() or set baselineOnMigrate to true to initialize the schema history table.
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:177)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:149)
> at org.flywaydb.core.Flyway.execute(Flyway.java:511)
> at org.flywaydb.core.Flyway.migrate(Flyway.java:149)
> at org.apache.nifi.registry.db.CustomFlywayMigrationStrategy.migrate(CustomFlywayMigrationStrategy.java:88)
> at org.springframework.boot.autoconfigure.flyway.FlywayMigrationInitializer.afterPropertiesSet(FlywayMigrationInitializer.java:62)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1855)
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1792)
> ... 98 common frames omitted {code}
> Looks like the issue is because Flyway changed their default table name at some point.
> https://github.com/flyway/flyway/issues/1848
> The issue does not happen going from 0.7.0 to 0.8.0, or 0.3.0 to 0.7.0, which is probably because 0.8.0 changed the Flyway version from 5.x to 6.x.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)