[Geoserver-devel] [jira] (GEOS-6616) Better management of attribute cache information

GeoServer GeoServer Developer
1

Jody Garnett created an issue

GeoServer / BugGEOS-6616

Better management of attribute cache information

Issue Type:

BugBug

Affects Versions:

2.4.8, 2.5.3, 2.6-RC1

Assignee:

Jody Garnett

Components:

REST

Created:

14/Aug/14 6:14 PM

Priority:

CriticalCritical

Reporter:

Jody Garnett

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

Add Comment

Add Comment

This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c)

Atlassian logo