Promoting the Denodo Lakehouse Accelerator¶

Each Denodo environment should have its own Denodo Lakehouse Accelerator cluster configured, so for each environment you have a Denodo cluster and an Denodo Lakehouse Accelerator 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 a Lakehouse Accelerator cluster that is configured and scaled according to the expected workload of each scenario.

Deployment and Registration

The Denodo Lakehouse Accelerator cluster can be deployed following the instructions in the Denodo Lakehouse Accelerator Guide. 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 Lakehouse Accelerator. You should use this option to create this necessary metadata on each environment, instead of promoting the embedded Lakehouse Accelerator data source using the Solution Manager.

Promoting Changes

Once the Denodo Lakehouse Accelerator is configured in each environment, you can promote subsequent changes normally using the Solution Manager. For example:

• Bulk Load Configuration: If you configure bulk load settings or update credentials for an object storage route, you can include the data source in a revision to update the target environment.

• Object storage routes: If you create a new base view over a route defined in your Lakehouse Accelerator data source, you can promote that view as usual:

  • Data Source Inclusion: Remember to include the data source in your revision if it references a route that does not yet exist or has been modified in the target environment.

  • Environment-Specific Routes: The object storage routes defined at the data source are environment-specific, which means you can provide a different value on the target environment.

  • Dataset Names: By default, the name of the dataset in storage is not environment-specific, as it is typically the same across all environments.

  • Handling Delta Lake Exceptions: In certain scenarios, such as when accessing Delta Lake tables, dataset names may differ between environments. In these cases, you can enable environment-specific values by setting the following property:

SET 'com.denodo.embeddedmpp.wrapperExternalPathEnvironmentSpecificEnabled' ='true'

For further details on handling environment-specific elements across different environments, refer to the sections Exporting and Importing Elements Across Different Environments and also Validate a Revision in the Solution Manager Administration Guide.