Upgrade to Embedded MPP 9¶

These are the general steps to follow:

1. Migrate values.yaml.

   Compare values.yaml from versions 8.0 and 9 by making a diff of both files. Each difference will indicate either new properties added in version 9 or overridden values specific to your deployment.

2. Migrate catalogs.

   • If you have added new catalogs in the form of property files to the presto/conf/catalog folder you have to add them in the new catalog folder. Although the recommended way is to add them in values.yaml to avoid this step in future migrations:

   # -- Additional catalogs, as an example the jmx catalog
   catalog:
     # jmx: |-
     #   connector.name=jmx
   

   • If you have added new properties to your hive, iceberg or delta catalogs you have to add them in the new catalog files. Although the recommended way is to add them in values.yaml to avoid this step in future migrations:

   hive: iceberg: delta:
     # -- Entries for extra config properties for catalog
     additionalConfig: [
       #-Dprop=value,
       #-Dprop=value
     ]
   

   • If you have added new properties to the core-site.xml files you have to add them to the new core-site.xml files.

3. Migrate JVM properties.

   If you have added new properties to the presto/conf/jvm.config file, you have to add them in the new jvm.config file. Although the recommended way is to add them in values.yaml to avoid this step in future migrations:

   jvm:
     # -- Entries for extra JVM config properties
     additionalJVMConfig: [
       #-Dprop=value,
       #-Dprop=value
     ]
   

4. Migrate configuration properties.

   If you have added new properties to the presto/conf/config.properties.coordinator and presto/conf/config.properties.worker files, you have to add them in the new configuration files. Although the recommended way is to add them in values.yaml to avoid this step in future migrations:

   coordinator.additionalConfig and worker.additionalConfig:
     # -- Entries for extra config properties
     additionalConfig: [
       # query.max-memory-per-node=15GB,
       # query.max-total-memory-per-node=15GB,
       # query.max-memory=60GB
     ]
   

5. Create a backup of the Embedded PostgreSQL or the external database of the Embedded Hive Metastore.

   If you are using the Embedded PostgreSQL this backup is mandatory since upgrades to new major versions of PostgreSQL do not maintain backwards compatibility.

   You must create a manual dump before the upgrade and restore it before creating new tables in the Denodo Embedded MPP. To create the backup copy you can follow the instructions in the Embedded PostgreSQL Backup section.

   Once the manual dump is done, set postgresql.version15BackupWarning to false in values.yaml and continue with the installation upgrade of the Denodo Embedded MPP:

   helm upgrade prestocluster prestocluster/
   

   Once the new version of the MPP is deployed, you have to restore the backup following the instructions in the Embedded PostgreSQL Backup section.

   Important

   Starting with version 202509 of the Denodo Embedded MPP, the version15BackupWarning property is deprecated. PostgreSQL 15 was introduced in version 20240506, so this warning will be removed in a future release.