ContentDataStore inefficient verification of available content entries
The code now scans all the source feature types names for each getFeatureSource against a not yet used FeatureType (e.g., for 1000 feature types, calling in order getFeatureSource on each of the feature types, causes 1000 calls to createTypeNames(), or in other terms, scanning and checking 1 million type names).
Cool, then I'll reopen it and I'll mark it for backport.
Not right now, apparently on the build server this is causing some OOM errors in the online build. I guess that user can access way too many tables (tens of thousands)
Is this something we can backport?
Thanks for the fix Andrea