georchestra / mapstore2-georchestra

geOrchestra newest viewer
Other
6 stars 23 forks source link

Project update to the latest MapStore 2024.02 #714

Closed tdipisa closed 1 month ago

tdipisa commented 1 month ago

Description

It is requested to update the project to the latest MapStore version. The MapStore revision need to be updated to the latest stable branch 2024.02.xx.

Checks

It is necessary to check if the existing customizations are properly working after the project update. Custom specific extensions that are involved as part of this update work are the following. These will be tested separately for:

Notes

The project need to be updated by following the official migration guidelines involved.

In particular in the master branch

Preliminary checks and tests for this update will be performed on https://georchestra.geo-solutions.it/

Release procedures to follow are reported in project README.

ElenaGallo commented 1 month ago

@tdipisa tests done, they are available here and here

tdipisa commented 1 month ago

@dsuren1 From functional tests performed it seems you have missed to add/consider the following in default config:

Can you please raise a PR to provide what is missing? Thank you so much.

landryb commented 4 weeks ago

to the ones trying the upgrade path to 2024.02, some notes:

so i followed https://docs.mapstore.geosolutionsgroup.com/en/latest/developer-guide/mapstore-migration-guide/#database-update, but had to manually adapt some bits

:/tmp $wget https://github.com/geosolutions-it/geostore/raw/refs/heads/master/doc/sql/migration/postgresql/postgresql-migration-from-v.2.0.0-to-v2.1.0.sql
:/tmp $sed -i -e 's/gs_resource/mapstore.gs_resource/' postgresql-migration-from-v.2.0.0-to-v2.1.0.sql
:/tmp $sed -i -e 's/geostore/mapstore/g' postgresql-migration-from-v.2.0.0-to-v2.1.0.sql
[localhost:5432] georchestra@georchestra=> \i /tmp/postgresql-migration-from-v.2.0.0-to-v2.1.0.sql
ALTER TABLE
Time: 29.472 ms
ALTER TABLE
Time: 0.681 ms
ALTER TABLE
Time: 11.099 ms
UPDATE 0
Time: 57.612 ms

with that done the db schema is updated, requests to the backend now succeed, and i see maps in the map loader/on /mapstore/#/home, and existing contexts on /mapstore/#/admin.

maybe geostoreEntityManagerFactory.jpaPropertyMap[hibernate.hbm2ddl.auto] should be set to update to ease upgrades ?