Jody Garnett created an issue |
Issue Type: |
Bug |
---|---|
Assignee: |
|
Created: |
28/Aug/14 5:59 PM |
Priority: |
Major |
Reporter: |
The operation of DELETE layer and DELETE featureType are not consistent.
This is the first of two issues created as a follow up to GEOS-6575 and GEOS-6575. These issues describe the use of the REST api to kick GeoServer into noticing when new columns have been added to a PostGIS database.
The use of DELETE featureType recurse=true resets the DataStore connection in order to clear the cache of attributes.
- Previously the DataStore “reset” was implemented using DataStore.dispose() followed by creating a new DataStore - resulting in the failure of concurrent described in GEOS-6575.
- The use of DataStore “reset” now makes use of ContentEntry.flush() if available as described in
GEOS-6616
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) |