-
Notifications
You must be signed in to change notification settings - Fork 8.2k
Hibernate Validator is enabled by default when not used #45677
Copy link
Copy link
Labels
area/dist/quarkusarea/performancekind/bugCategorizes a PR related to a bugCategorizes a PR related to a bugpriority/importantMust be worked on very soonMust be worked on very soonrelease/26.5.3release/26.6.0team/cloud-native
Description
Before reporting an issue
- I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.
Area
dist/quarkus
Describe the bug
The Hibernate Validator is enabled by default, even when it's not used currently. The Hibernate Validator is only used for the new Client API v2 right now. Enabling Hibernate Validator is quite resource-consuming for startup due to expensive initialization. That's also a difference between 26.4.x and 26.5.x, so it's considered as regression.
Startup time:
Startup memory allocations (against 26.4.x) (~10MB with other related procedures):
Version
26.5.1
Regression
- The issue is a regression
Expected behavior
Hibernate Validator is not enabled when not needed
Actual behavior
Hibernate Validator is always enabled
How to Reproduce?
Start the server and see enabled Quarkus extensions
Anything else?
Might contribute to:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/dist/quarkusarea/performancekind/bugCategorizes a PR related to a bugCategorizes a PR related to a bugpriority/importantMust be worked on very soonMust be worked on very soonrelease/26.5.3release/26.6.0team/cloud-native