-
Notifications
You must be signed in to change notification settings - Fork 989
Postgres Driver - Flyway non-empty schema "public" without metadata table #503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I am using the following sqldao in conf:
|
Maybe dropping the database and re-creating it would fix it. |
I created a dedicated db for spark-jobserver and it worked fine, thanks noorul. Getting next issue which seems to be #486 Migration V0_7_0__init_tables.sql failedSQL State : 42601 |
Since you are using postgresql, you should not see this getting executed. |
This flyway.locations="db/postgresql/migration" should be at the root level, not inside jobserver namespace |
I moved flyway.locations outside jobserver scope but didn't change anything :( EDIT: worked fine @noorul !
|
Closing |
Uh oh!
There was an error while loading. Please reload this page.
I've tried the postgres sqldao driver in version 0.6.2 and I am encountering the following error
Caused by: org.flywaydb.core.api.FlywayException: Found non-empty schema "public" without metadata table! Use baseline() or set baselineOnMigrate to true to initialize the metadata table.
at org.flywaydb.core.Flyway$1.execute(Flyway.java:1035)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:1006)
at org.flywaydb.core.Flyway.execute(Flyway.java:1418)
at org.flywaydb.core.Flyway.migrate(Flyway.java:1006)
at spark.jobserver.io.JobSqlDAO.init(JobSqlDAO.scala:103)
at spark.jobserver.io.JobSqlDAO.(JobSqlDAO.scala:88)
... 16 more
After some research I've found that we should put initOnMigrate to true, is it a viable solution or is there another issue I could fix? Thanks
The text was updated successfully, but these errors were encountered: