Hi, We are facing problem with the recreation of existing indexes when hbm2ddl.auto is set to ‘update’. We have tables with millions of data and it is dropping the existing indexes and creating again (which is taking too long to start the server). Blockquote For example: I can see the following…

This behaviour is expected using ddl-auto=update and luckly it’s configurable. Hibernate contains following key: hibernate.schema_update.unique_constraint_strategy where: DROP_RECREATE_QUIETLY: Default option. Attempt to drop, then (re-)create each unique constraint. Ignore any exceptions being t…

Hbm2ddl.auto=update recreating existing indexes after drop

Hibernate ORM

drahkrub July 6, 2020, 2:26pm 8

ping @sebersole - do you know the reason for the re-creation of unique indexes? Or does it make more sense to open a jira ticket right away?

Topic		Replies	Views
Hibernate tries to drop existing index Hibernate ORM	0	403	March 17, 2020
Hibernate 5 hbm2ddl.auto=update doesn't work Hibernate ORM	2	4368	November 7, 2018
Hibernate 5.2.14 ddl update tries to recreate tables in Oracle Hibernate ORM	10	7268	June 12, 2018
I would really like to know more about the update!! Hibernate ORM	1	361	June 21, 2021
How to evict Hibernate second cache when tables were changed by ddl-auto: update? Hibernate ORM	3	507	October 31, 2022

Hbm2ddl.auto=update recreating existing indexes after drop

Related topics