In Relation To

In 5.3, Hibernate ORM started to fail at bootstrap when one of your entity/collection/query caches was not available: ORM did not create the caches anymore and relied on you having declared explictly all the necessary caches. This change was made because, if we automatically create caches without a sane configuration, your caches could be very badly configured (no size limit, no expiration time for instance) and that could ultimately lead to unwanted behaviors (namely OOM issues).

While it’s certainly a good thing to configure your caches, we decided to soften this constraint and, starting with 5.3.2, Hibernate ORM will raise warnings for all the non-existing caches and create them. Of course, you are still very much encouraged to configure properly your caches (either by defining a sane default configuration in your cache implementation or by declaring explicitly each cache).

This should improve ORM usability while still being safe enough. You can configure this behavior by using the hibernate.javax.cache.missing_cache_strategy property. See our documentation for more information.

Long story short, the names of the query cache regions have changed in 5.3.2: they are now short names that will be stable (prior to that, they were tied to internal class names so subject to changes when we refactored things).

The new names are:

Note that if you haven’t configured your caches with these new names, we will still try to use the caches with the old names so it shouldn’t require any changes on your part.