Description
Hi,
in our application we have currently set:
hibernate.cache.use_second_level_cache: false
hibernate.connection.provider_class: "Some NOOP class"
leading to the following warnings in current LTS:
Persistence-unit [] sets unsupported properties that override Quarkus' own settings. These properties may break assumptions in Quarkus code and cause malfunctions. If this override is absolutely necessary, make sure to file a feature request or bug report so that a solution can be implemented in Quarkus. Unsupported properties that override Quarkus' own settings: [hibernate.cache.use_second_level_cache]
Persistence-unit [] sets unsupported properties. These properties may not work correctly, and even if they do, that may change when upgrading to a newer version of Quarkus (even just a micro/patch version). Consider using a supported configuration property before falling back to unsupported ones. If there is no supported equivalent, make sure to file a feature request so that a supported configuration property can be added to Quarkus, and more importantly so that the configuration property is tested regularly. Unsupported properties being set: [hibernate.cache.use_second_level_cache, hibernate.persister.resolver]
As we implement out own caching and have a separate persistence layer implemented on our own (we have high performance requirements), we feel these properties to be necessary.
Kind regards,
Stefan
Implementation ideas
No response
Description
Hi,
in our application we have currently set:
hibernate.cache.use_second_level_cache: false
hibernate.connection.provider_class: "Some NOOP class"
leading to the following warnings in current LTS:
Persistence-unit [] sets unsupported properties that override Quarkus' own settings. These properties may break assumptions in Quarkus code and cause malfunctions. If this override is absolutely necessary, make sure to file a feature request or bug report so that a solution can be implemented in Quarkus. Unsupported properties that override Quarkus' own settings: [hibernate.cache.use_second_level_cache]
Persistence-unit [] sets unsupported properties. These properties may not work correctly, and even if they do, that may change when upgrading to a newer version of Quarkus (even just a micro/patch version). Consider using a supported configuration property before falling back to unsupported ones. If there is no supported equivalent, make sure to file a feature request so that a supported configuration property can be added to Quarkus, and more importantly so that the configuration property is tested regularly. Unsupported properties being set: [hibernate.cache.use_second_level_cache, hibernate.persister.resolver]
As we implement out own caching and have a separate persistence layer implemented on our own (we have high performance requirements), we feel these properties to be necessary.
Kind regards,
Stefan
Implementation ideas
No response