-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Since 3.1.2 (#33873) Hibernate schema validation seems flaky and fails due missing tables #34187
Comments
As far as I know we don't experience that in our integration test suite. Please provide a reproducer, even if it's flaky. |
Unfortunately, I was not able to implement a shareable reproducer. I tried one with long running migrations, but this seems not to trigger it. The issue is still present with the newest quarkus version. Maybe the stacktrace does help to see a potential timing issue?
|
I don't think we'll be able to do much without a sample that reproduces the issue (at least some of the time) |
Fair enough. As we initialize the datasource during runtime and therefor starting the db migration manually, we kind of workaround this issue. |
Gotcha, thanks for the update. |
With #33873 the moment of execution of Liquibase/Flyway migration has change to a later point of the startup process.
Since this change I experience flaky Hibernate schema validation errors
org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [myTable]
on startupDo we now have a race condition between hibernate schema validation and schema migration?
The text was updated successfully, but these errors were encountered: