Promoting the Denodo Embedded MPP

Each Denodo environment should have its own Denodo Embedded MPP cluster configured, so for each environment you have a Denodo cluster and an MPP cluster that can communicate to each other. From a security perspective this ensures each environment is isolated and from a performance perspective this ensures each environment has an MPP cluster that is configured and scaled according to the expected workload of each scenario.

The Denodo Embedded MPP cluster can be deployed following the instructions in the Presto cluster on Kubernetes user manual. This deployment process includes a final step that creates a new special data source in Denodo called “embedded_mpp”. This step is described in detail in Section Register Presto as Denodo’s MPP. You should use this option to create this necessary metadata on each environment, instead of promoting the embedded MPP data source using the Solution Manager.

Registering the Denodo Embedded MPP data source in different environments

Once you have the Denodo Embedded MPP configured on each environment you can promote any changes normally using the Solution Manager. For example, if you configure bulk load on your embedded MPP data source and configure the credentials to access the object storage of your choice you can include the data source in a revision to update the data source on the target environment. The same happens if you create a new base view over one of the routes defined on your embedded MPP data source. You can promote your base view normally, just remember to include the data source in case it has been created over a route that does not exist yet on the target environment or over a route that has been modified.

Add feedback