USER MANUALS

Changes in Denodo Platform 9

This section lists the changes introduced in version 9.0 of the Denodo Platform (that is, 9 without updates) compared to the previous version (8.0).

Read this if you are going to upgrade from Denodo 8.0 or earlier.

Changes that Apply to All the Modules of the Denodo Platform and Solution Manager

Export and Import Metadata/Settings

Important

Right after you install the Denodo Platform or the Solution Manager, do this post-installation task: Replicate the Encryption Key Across All the Installations.

If you do not do this, this installation may be left in an inoperable state. Do not start any of the components of the Denodo Platform before doing this.

Versioning

The name of the major version is 9, not 9.0, unlike in previous versions in which the major version is 8.0, 7.0, etc.

The updates will no longer be designated by date. Instead, the second “number” of the version represents “the update”. That is, 9.0 is an installation of 9 without updates, 9.1 is the first update, 9.2 the second, etc. We will provide more details about this with the release of the first update.

Web Container

  • The version is now Tomcat 10.x; in Denodo 8.0, is Tomcat 9.x.

  • The default amount of memory is now 2 gigabytes; in Denodo 8.0 it was 1. That is, the default value of -Xmx is now 2 gigabytes.

Java 17

  • Denodo 9 ships with Java 17; Denodo 8.0 ships with Java 11.

  • All the components of the Denodo Platform and Solution Manager now run with Java 17. You can still load the Denodo JDBC driver from applications that run with Java 11 (as in Denodo 8.0). See more details at Supported Java Development Kits (JDK).

  • When exporting metadata, the command to create the extension associated to a custom policy is always CREATE OR REPLACE JAR, instead of DROP followed by CREATE.

SSL/TLS Configuration

  • Denodo Platform SSL configuration can now be configured using PKCS12 keystores. In previous versions, you could only use a keystore with the format JKS. See more about this in the section Enable SSL/TLS in the Denodo Platform.

Virtual DataPort

  • The connections to data sources with TLS 1.0 are disabled by default. It is unlikely your sources still use TLS 1.0 because it has been considered insecure for years. One of the steps during the process of upgrading to Denodo 9 is to test all the data sources so if you are affected by this problem, you will detect it quickly. If one of your data sources still uses TLS 1.0, contact the administrators of that source to upgrade to a more secure version of TLS. If that is not possible, contact Denodo Support to get the steps of how to enable TLS 1.0.

Virtual DataPort - Security

  • Non-admin users are now allowed to impersonate other users when executing a query if they have the impersonator role assigned. This feature is disabled by default; to enable it, execute this command:

    SET 'com.denodo.vdb.security.allowImpersonateToRegularUsers' = 'true';

    In 8.0 only administrator users with the role impersonator were allowed to impersonate in queries.

  • VCS actions now support exporting dependencies across databases by default.

Virtual DataPort - JMS listeners

In Denodo 9, the JMS API was upgraded to Jakarta Messaging API. Because of this, old JMS connectors that work with previous versions of Denodo may not work with Denodo 9. For instance, the connector of ActiveMQ 5.x, which implements the API Javax JMS, must be replaced with the connector of ActiveMQ 6.x, which implements the API Jakarta JMS.

Virtual DataPort - ODBC Data Sources

In Denodo 9, the feature to create ODBC data sources is disabled by default. Some years ago, starting with the release of Denodo 8.0, the capability of creating ODBC data sources was deprecated. See more in the section Enabling the Support for ODBC Sources.

Virtual DataPort - JDBC Data Sources

  • The following JDBC driver are no longer distributed in Denodo 9 because they were old versions that were no longer supported:

    • Amazon Redshift driver version 1.x (with classpath ‘amazon-redshift’)

    • Databricks driver version 1 (with classpath ‘databricks’)

    • Oracle 12c driver version v12.2.0.1 (with classpath ‘oracle-12c-v12.2.0.1’)

Virtual DataPort - JDBC Driver

  • The value of the driver property idleKeepAlive is now true; in previous versions it is false.

Virtual DataPort - Other Data Sources

  • When you create a data source with an HTTP route, the option Check certificates is now selected by default; before it was cleared by default. This helps the system to be secure by default. Note that this does not affect data sources that you import from previous versions during the upgrade process.

  • LDAP channel binding over TLS/SSL is now enabled by default in LDAP data sources (since the current Java version already supports this feature). You no longer need to execute the following command to enable this feature:

    SET 'com.denodo.vdb.misc.datasource.LDAPDataSource.sasl.channelBindingEnabled' = 'true';

Other Changes

  • The default user agent used by Denodo has been changed from “Mozilla/5.0 (compatible; MSIE 5.5; Windows NT 5.0)” to “Denodo”.

  • It is now possible to modify the behavior of predefined delegable functions with custom functions. See more information in this section Creating Custom Functions with Annotations

  • In Denodo 8.0 and earlier versions, Virtual DataPort runs on Linux under heavy load and in certain scenarios, you may have had to set up the environment variable MALLOC_ARENA_MAX. In Denodo 9, this is no longer necessary; by default Virtual DataPort sets this variable to MALLOC_ARENA_MAX=4. However, you can still set this environment variable if you want.

  • Resource Manager: now, the query fails with an error when the row limit is reached for the action: Stop Query action when the maximum number of rows returned has been reached.

Design Studio

  • When exporting VQL with dependencies it will include by default dependencies that are in other databases.

  • In the panel SUMMARY of the views and stored procedures, the button Execution Panel has been renamed to Query.

  • In the dialog File > Export, the label “Include extensions and libraries” has been renamed to “Include extensions, libraries and server configuration files”.

These changes have also been implemented in Administration Tool.

Scheduler

The following properties are no longer included in Scheduler and Scheduler-Index backups. When importing backups from Denodo 8.0, these properties will be ignored:

  • com.denodo.security.ssl.*

  • ComplexDataSource

Solution Manager

  • The properties related to the SSL settings have been renamed. Now they have the suffix .secret. (see Enabling SSL/TLS in Solution Manager Servers).

  • The SQL scripts of Solution Manager are now in <SOLUTION_MANAGER_HOME>/scripts/solution-manager/sql. In Denodo 8.0, these scripts are in <SOLUTION_MANAGER_HOME>/conf/solution-manager/sql.

Diagnostic & Monitoring Tool

  • Query CPU usage graph polling interval setting is no longer included in the User Configuration -> Threads Configuration. Now it will be 5 seconds by default and non-configurable.

User Manuals

Add feedback