This change includes a flyway upgrade which causes a default table name change for where flyway looks for migrations.

If SO does not work, please check your database for a table called 'schema_version' in requests and catalog db. If you have this table, there are two choices:

1. Rename the table 'flyway_schema_history'
2. Add flyway.table=schema_version to the application.yaml for requests and catalog db

Source:
https://stackoverflow.com/questions/49063385/flyway-5-0-7-warning-about-using-schema-version-table