As Andrea mentioned last meeting we are looking at January for a GeoServer 2.7 feature freeze.
One of the things that tripped me up with GeoServer 2.6 was debugging the REST API around deleting layers and feature types. I would like to change the api so delete feature type recuse=true and delete layer recurse=true are consistent.
|
Operation |
Recurse |
FeatureTypeInfo |
LayerInfo |
LayerGroup |
DataStore |
attributes |
schema |
|---|---|---|---|---|---|---|---|
|
DELETE layer |
false |
|
fail |
||||
|
DELETE layer |
true |
|
|
|
|
|
|
|
DELETE featureType |
false |
|
fail |
fail |
reset |
|
flush |
|
DELETE featureType |
true |
|
|
fail |
reset |
|
flush |
It is not clear to me if the recommendation below is an API change (requiring a proposal) or a quality assurance issue (which could be back ported to 2.6 series).
Recommendation- Change DELETE layer recurse=true flushes any cached attribute information (resetting the datastore if necessary)
- Change DELETE featureType recurse=true to remove layer from layer groups
This would make the two operations functionally identical, but would not represent an API regression.
|
Operation |
Recurse |
FeatureTypeInfo |
LayerInfo |
LayerGroup |
DataStore |
attributes |
schema |
|---|---|---|---|---|---|---|---|
|
DELETE layer |
false |
|
fail |
||||
|
DELETE layer |
true |
|
|
|
reset |
|
flush |
|
DELETE featureType |
false |
|
fail |
fail |
reset |
|
flush |
|
DELETE featureType |
true |
|
|
|
reset |
|
flush |
The issue is here: https://jira.codehaus.org/browse/GEOS-6636. There is an alternate provided for that ticket if anyone does not like the recommendation above.
ยทยทยท
Jody Garnett