You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using ClassPathScanningCandidateComponentProvider with an RegexPatternTypeFilter include filter prevents use of the component index.
It might be worth to evaluate regex on the component index so Spring Data's custom repository implementation scan could benefit from component-index-based scanning. RegexPatternTypeFilter is used on every scan to limit component candidates with a simple class name.
It also might be worth introducing a SimpleClassNameTypeFilter dedicated to this style of filtering to eliminate regex pattern compilation and the associated matching cost.
Mark Paluch opened SPR-16010 and commented
Using
ClassPathScanningCandidateComponentProvider
with anRegexPatternTypeFilter
include filter prevents use of the component index.It might be worth to evaluate regex on the component index so Spring Data's custom repository implementation scan could benefit from component-index-based scanning.
RegexPatternTypeFilter
is used on every scan to limit component candidates with a simple class name.It also might be worth introducing a
SimpleClassNameTypeFilter
dedicated to this style of filtering to eliminate regex pattern compilation and the associated matching cost.No further details from SPR-16010
The text was updated successfully, but these errors were encountered: