+1 Cheers, Torben
On Fri, Aug 5, 2022 at 9:18 AM Simone Giannecchini < simone.giannecch...@geosolutionsgroup.com> wrote: > +0 > > Regards, > Simone Giannecchini > == > Professional Support for GeoNode, GeoServer and MapStore from the experts! > Visit https://www.geosolutionsgroup.com/enterprise-support-services for > more information. > == > Ing. Simone Giannecchini > @simogeo > Founder/Director GeoSolutions Italy > President GeoSolutions USA > > phone: +39 0584 962313 > fax: +39 0584 1660272 > mob: +39 333 8128928 > US: +1 (845) 547-7905 > > http://www.geosolutionsgroup.com > http://twitter.com/geosolutions_it > > ------------------------------------------------------- > 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. > > > On Fri, Aug 5, 2022 at 4:12 PM Andrea Aime < > andrea.a...@geosolutionsgroup.com> wrote: > >> I've made a PR mixing the proposal with some of the indications contained >> in GEOS-6637, here: >> https://github.com/geoserver/geoserver/pull/6093 >> >> I've tried to keep changes to a minimum, as I'd like to backport these >> changes down to 2.20.x >> (it's to support GeoNode layer reconfiguration). >> >> Cheers >> Andrea >> >> On Thu, Aug 4, 2022 at 11:12 AM Andrea Aime < >> andrea.a...@geosolutionsgroup.com> wrote: >> >>> On Wed, Aug 3, 2022 at 8:34 PM Jody Garnett <jody.garn...@gmail.com> >>> wrote: >>> >>>> +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. >>>> >>> >>> Ah found it, https://osgeo-org.atlassian.net/browse/GEOS-6616, was >>> originally implemented in the FeatureTypeResource and then >>> moved into the ResourcePool: >>> >>> https://github.com/geoserver/geoserver/commit/8fed80df5ca72d0d89ad42fe8b19b9fe77b2ea72 >>> >>> >>>> >>>> 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). >>>> >>> >>> I was like... uh, never heard of it, is it already there? And then >>> realized it never got worked on. >>> Yes, I would mark it as duplicate. >>> >>> >>>> >>>> 3) Is there anything else to reset? >>>> >>>> I notice that reloading the catalogue is used to reset icon caches and >>>> user projections. >>>> >>> >>> Yes, there is more to reset. Quoting from the proposal: >>> >>> https://github.com/geoserver/geoserver/wiki/GSIP-214#motivation >>> >>> "Provide an explicit, clear, reliable cache reset API for stores, >>> coverages and feature types (other cache resets are out of scope, but could >>> be added by willing contributors)." >>> >>> 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 >>> >> >> >> -- >> >> Regards, >> >> Andrea Aime >> >> == >> 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 >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
