|
Quick follow up to testing GEOS-6575 in an abusive clustered environment.
-
Good news: Removing several calls to clear the ResourcePool datastore cache was effective
-
Bad news: clearing of the DataStore cache was being used as an undocumented way of forcing GeoServer to recognise when database columns had been added or removed
DELETE
-
Quickly restore previous "burn the ground" functionality to FeatureType DELETE
-
Special case in a call to ContentState.flush() to allow JDBCDataStore implementations to detect the addition of additional columns without full on reset effecting other FeatureTypes
PUT / PUSH
Can look at introducing a call to ContentState.flush() before geotools schema is used to in the production/validation of FeatureTypeInfo
|