Changes between Version 210 and Version 211 of Versions


Ignore:
Timestamp:
Mar 26, 2022, 7:23:21 AM (4 years ago)
Author:
Dimitar Misev
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Versions

    v210 v211  
    88Alternative ways of obtaining rasdaman are listed in the [wiki:Download] area.
    99
    10 == Version 10.0
     10== Version 10.0.1 (2022-03-28)
     11
     12=== Bug fixes
     13
     14- OGC frontend (petascope)
     15 - Fixed leak of large binary objects in PostgreSQL which were left in petascopedb when removing data, e.g. dropping a coverage, pyramid levels, styles, etc; these objects will be properly and automatically removed via triggers from now on.
     16
     17  However, the already leaked orphan objects cannot be automatically removed, and require the following steps to address in order to reduce the size of petascopedb:
     18{{{
     19#!sh
     20# Stop rasdaman and embedded petascope if exists
     21sudo service rasdaman stop
     22# If petascope runs on external tomcat, then stop it
     23sudo service tomcat9 stop
     24# Rename the existing petascopedb to petascopedb_backup
     25sudo -u postgres psql -c "ALTER DATABASE petascopedb RENAME TO petascopedb_backup"
     26# Create a new empty database
     27sudo -u postgres createdb petascopedb
     28# Change in petascope.properties
     29metadata_url=jdbc:postgresql://localhost:5432/petascopedb_backup
     30# Finally, run migration script to copy only the relevant data from
     31# petascopedb_backup to the new petascopedb
     32/opt/rasdaman/bin/migrate_petascopedb.sh
     33# Start rasdaman (and Tomcat if needed)
     34sudo service rasdaman start
     35sudo service tomcat9 start
     36# Verify that services are working as expected, if all is fine the
     37# petascopedb_backup can be dropped from PostgreSQL (but maybe consider
     38# exporting it to a backup first)
     39sudo -u postgres dropdb petascopedb_backup
     40}}}
     41
     42=== Full list of commits
     43
     44'''Addressed tickets''' between v10.0.0 and v10.0.1 with 3 commits:
     45{{{
     46#!sh
     47echo "||= changeset =||= author =||= ticket =||= subject =||" && \
     48git log --pretty=format:"|| changeset:%h || %an || %s" v10.0.0..v10.0.1 | sort -k 3 -t ':' -n | sed 's/ticket:\([0-9]*[^ ]\) -* */ticket:\1 || /'
     49}}}
     50|| changeset:e460270cb || Bang Pham Huu || ticket:2522 || [FIX] wcst_import supports null values per band
     51|| changeset:a853b3ba1 || Dimitar Misev || ticket:2542 || add details on patch submission to the docs
     52|| changeset:1b880ecf8 || Bang Pham Huu || ticket:2564 || FIX - postgresql - create triggers for cleaning large objects (CLOB) of TEXT type when update / remove
     53
     54
     55
     56== Version 10.0.0 (2022-03-18)
    1157
    1258=== New features, enhancements, bug fixes
    … …  
    4995 - Support GDAL 3 when transforming coordinates with regards to EPSG CRS YX axis orders
    5096 - Allow non-ASCII characters in coverage metadata
    51  - (v10.0.1) Fixed leak of large binary objects in PostgreSQL which were left in petascopedb when removing data, e.g. dropping a coverage, pyramid levels, styles, etc; these objects will be properly and automatically removed via triggers from now on.
    52 
    53   However, the already leaked orphan objects cannot be automatically removed, and require the following steps to address in order to reduce the size of petascopedb:
    54 {{{
    55 #!sh
    56 # Stop rasdaman and embedded petascope if exists
    57 sudo service rasdaman stop
    58 # If petascope runs on external tomcat, then stop it
    59 sudo service tomcat9 stop
    60 # Rename the existing petascopedb to petascopedb_backup
    61 sudo -u postgres psql -c "ALTER DATABASE petascopedb RENAME TO petascopedb_backup"
    62 # Create a new empty database
    63 sudo -u postgres createdb petascopedb
    64 # Change in petascope.properties
    65 metadata_url=jdbc:postgresql://localhost:5432/petascopedb_backup
    66 # Finally, run migration script to copy only the relevant data from
    67 # petascopedb_backup to the new petascopedb
    68 /opt/rasdaman/bin/migrate_petascopedb.sh
    69 # Start rasdaman (and Tomcat if needed)
    70 sudo service rasdaman start
    71 sudo service tomcat9 start
    72 # Verify that services are working as expected, if all is fine the
    73 # petascopedb_backup can be dropped from PostgreSQL (but maybe consider
    74 # exporting it to a backup first)
    75 sudo -u postgres dropdb petascopedb_backup
    76 }}}
    77 
    7897
    7998- wcst_import
    … …  
    306325
    307326=== Full list of commits
    308 
    309 ==== v10.0.1 (2022-03-28)
    310 
    311 '''Addressed tickets''' between v10.0.0 and v10.0.1 with 3 commits:
    312 {{{
    313 #!sh
    314 echo "||= changeset =||= author =||= ticket =||= subject =||" && \
    315 git log --pretty=format:"|| changeset:%h || %an || %s" v10.0.0..v10.0.1 | sort -k 3 -t ':' -n | sed 's/ticket:\([0-9]*[^ ]\) -* */ticket:\1 || /'
    316 }}}
    317 || changeset:e460270cb || Bang Pham Huu || ticket:2522 || [FIX] wcst_import supports null values per band
    318 || changeset:a853b3ba1 || Dimitar Misev || ticket:2542 || add details on patch submission to the docs
    319 || changeset:1b880ecf8 || Bang Pham Huu || ticket:2564 || FIX - postgresql - create triggers for cleaning large objects (CLOB) of TEXT type when update / remove
    320327
    321328==== v10.0.0 (2022-03-18)