[Geoserver-devel] Feedbacks on deleting stores through REST

GeoServer GeoServer Developer
1

Hi list,

As you know, I’m working on a geotools improvement (see 1 for the proposal) to allow delete on Structured GridCoverage Readers.

I would like to integrate this capability in GeoServer through REST delete coverageStore call 2:
On such a topic I was thinking about adding a new parameter beside the “recurse” one 3 for the delete op.

Something like “delete” which may have 3 values:

none → default… to be backward compatible with the current REST delete store behaviour)

metadata → in order to delete only metadata, and auxiliary files… no granules will be deleted)

all → in order to delete everything. This will be related to the reader.delete(true) call which will also delete granules.

What do you think about it?
Suggestions for better parameter name and value names are also greatly appreciated.

I will open a JIRA with the outcome of the discussion.

Please, let me know.
Best Regards,
Daniele

== GeoSolutions will be closed for Christmas Holidays from 23/12/2013 to 06/01/2014 ==
Ing. Daniele Romagnoli
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

2

Hey Daniele,

Not sure if there was any movement one this but +1 from me. The only suggestion from a naming standpoint would be to make the parameter named “purge”, rather than “delete”.

-Justin

···

On Wed, Dec 18, 2013 at 10:41 AM, Daniele Romagnoli <daniele.romagnoli@anonymised.com> wrote:

Hi list,

As you know, I’m working on a geotools improvement (see 1 for the proposal) to allow delete on Structured GridCoverage Readers.

I would like to integrate this capability in GeoServer through REST delete coverageStore call 2:
On such a topic I was thinking about adding a new parameter beside the “recurse” one 3 for the delete op.

Something like “delete” which may have 3 values:

none → default… to be backward compatible with the current REST delete store behaviour)

metadata → in order to delete only metadata, and auxiliary files… no granules will be deleted)

all → in order to delete everything. This will be related to the reader.delete(true) call which will also delete granules.

What do you think about it?
Suggestions for better parameter name and value names are also greatly appreciated.

I will open a JIRA with the outcome of the discussion.

Please, let me know.
Best Regards,
Daniele

== GeoSolutions will be closed for Christmas Holidays from 23/12/2013 to 06/01/2014 ==
Ing. Daniele Romagnoli
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

Rapidly troubleshoot problems before they affect your business. Most IT
organizations don’t have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk

Geoserver-devel mailing list
Geoserver-devel@anonymised.comt
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Justin Deoliveira
Vice President, Engineering | Boundless
jdeolive@anonymised.com
@j_deolive

3

Thanks for your feedback Justin,
I have created a JIRA for that, including your “purge” parameter suggestion.

Regards,
Daniele

···

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Daniele Romagnoli
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

On Mon, Jan 6, 2014 at 6:49 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:

Hey Daniele,

Not sure if there was any movement one this but +1 from me. The only suggestion from a naming standpoint would be to make the parameter named “purge”, rather than “delete”.

-Justin

On Wed, Dec 18, 2013 at 10:41 AM, Daniele Romagnoli <daniele.romagnoli@anonymised.com> wrote:

Hi list,

As you know, I’m working on a geotools improvement (see 1 for the proposal) to allow delete on Structured GridCoverage Readers.

I would like to integrate this capability in GeoServer through REST delete coverageStore call 2:
On such a topic I was thinking about adding a new parameter beside the “recurse” one 3 for the delete op.

Something like “delete” which may have 3 values:

none → default… to be backward compatible with the current REST delete store behaviour)

metadata → in order to delete only metadata, and auxiliary files… no granules will be deleted)

all → in order to delete everything. This will be related to the reader.delete(true) call which will also delete granules.

What do you think about it?
Suggestions for better parameter name and value names are also greatly appreciated.

I will open a JIRA with the outcome of the discussion.

Please, let me know.
Best Regards,
Daniele

== GeoSolutions will be closed for Christmas Holidays from 23/12/2013 to 06/01/2014 ==
Ing. Daniele Romagnoli
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

Rapidly troubleshoot problems before they affect your business. Most IT
organizations don’t have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Justin Deoliveira
Vice President, Engineering | Boundless
jdeolive@anonymised.com
@j_deolive