+1 It is a good topic to fix and I like the proposal. "quick last minute proposal" - with foss4g timing I expect we will need to adjust the release schedule until after the conference; it takes some time to set-up a new branch and jobs and I would prefer to see that done on the new build server.
1) The content datastore flushDataStore() functionality was added in 2015 based on customers who were using DELETE to remove a layer, and then added it again, in order to reset bounds and feature type information. 2) The issue https://osgeo-org.atlassian.net/browse/GEOS-6637 proposed a fix based on existing "?recalculate=nativebbox,latlonbbox" use, discussion led to: refresh= - alias recalcualte= (do not recalculate anything to avoid slow database access) * refresh=nativebbox - alias recalculate=nativebbox * refresh=latlonbbox - alias recalcualte=latlonbbox * refresh=attributes - regenerate attributes (clears ContentEntry, or reset older DataStores) * refresh=datastore - dispose/create DataStore I think your proposal can replace GEOS-6637 (or be marked as a duplicate). 3) Is there anything else to reset? I notice that reloading the catalogue is used to reset icon caches and user projections. -- Jody Garnett On Wed, 3 Aug 2022 at 10:07, Andrea Aime <andrea.a...@geosolutionsgroup.com> wrote: > Hi all, > a quick last minute proposal to have more focused, and clear, REST API to > reset specific resource caches: > > https://github.com/geoserver/geoserver/wiki/GSIP-214 > > Please discuss and vote. > > Cheers > Andrea > > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > ------------------------------------------------------- > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
