[hibernate-issues] [JIRA] (HHH-16207) Restore integration test coverage for the SchemaExport usage in Quarkus

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16207 ( https://hibernate.atlassian.net/browse/HHH-16207?atlOrigin=eyJpIjoiYzlmNz... ) Re: Restore integration test coverage for the SchemaExport usage in Quarkus ( https://hibernate.atlassian.net/browse/HHH-16207?atlOrigin=eyJpIjoiYzlmNz... ) About adding a nice SPI… Remember how this whole code in Quarkus is a hack that runs in an integrator, because we need the metadata to generate scripts, and the metadata is no longer available after we build the session factory? Well… now the metadata is in the session factory; it’s stored in the SchemaManager , which allows creating/dropping the schema at runtime: https://github.com/hibernate/hibernate-orm/blob/ed956d514a74417125b141d55... ( https://github.com/hibernate/hibernate-orm/blob/ed956d514a74417125b141d55... ) I thought we didn’t want to keep the metadata around at runtime, because it’s huge and leads to increased memory consumption? I thought we wanted that stuff garbage-collected ASAP? It’s probably also a problem when compiling to native as having those classes around will lead to many more classes/methods being included in executables… Though maybe that’s only a problem if there is actually code that uses the SchemaManager. Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) any opinion on this? Did you detect increased memory usage or higher native binary size in your benchmarks? ( https://hibernate.atlassian.net/browse/HHH-16207#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16207#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100216- sha1:3fa9804 )