What Is New in Denodo 8.0 Update 8.0u20220815¶
This page lists the main enhancements of the update 8.0u20220815 of the Denodo Platform and the Solution Manager. We also published these videos that explain the enhancements included in this update:
For a full list of enhancements and bug fixes, read the Release Notes of the update, in the Support Site or inside the zip file of the update.
When creating a flatten view, you can now flatten more than one array in the same view. Before, if a view had several arrays, you had to create one flatten view per array you wanted to flatten.
Virtual DataPort can now subscribe to events published by an Apache Kafka server, execute a query using the information included in the events and optionally, publish the result of the queries (see Kafka Listeners). This feature works similarly to the feature JMS listeners (Java Message Service) that was already available, but for Kafka instead of JMS.
New function JSONPATH. It extracts text from a JSON document, using a “JSON expression”.
Virtual DataPort (Data Sources)
There two new features that make it easier to consume data from REST APIs:
You can now use the same XML or JSON data source to create several base views. Now you enter the “base URL” of the API in the data source (e.g., https://www.acme.com/api) and when you create the base view, you provide the of the operation (e.g., “/customer”) and select the HTTP method (GET, PUT…). Before, the URL of the operation was stored in the data source so you had to create one data source for each operation of the REST API.
The main benefit is that you define the authentication, pagination options, proxy settings… in one data source and all the base views of this data source will use these options. You no longer have to duplicate the credentials on multiple data sources.
All the existing data sources keep working as usual, this is only for new data sources.
You can now create JSON and XML data sources based on the OpenAPI/Swagger document of a REST API. To use this, open the wizard to create a JSON or XML data source and select From OpenAPI 3 document, indicate the URL of the OpenAPI document and click Load default values. When clicking Create base view, Design Studio and the Administration Tool display the operations defined in the OpenAPI document (like when creating a JDBC base view) and you select the operations over which you want to create a base view.
This makes it easier to consume data from a REST API because you do not need to know the URL of each operation.
DF, JSON, XML and Excel data sources can now retrieve data from AWS S3.
New JDBC adapters:
GCP Cloud SQL for MySQL (also for the Cache Engine).
GCP Cloud SQL for PostgreSQL (also for the Cache Engine).
Microsoft SQL Server 2019
Virtual DataPort (Cache Engine)
Incremental cache loads updating the existing cached data: this support is now available for BigQuery, to cache data and for creating remote tables. (list of databases for which Denodo supports incremental loads).
You can now customize the DDL statements that the cache engine executes to create the tables in the cache database, and the commands to create remote tables and materialized tables. You have to use this feature executing VQL statements (see section JDBC Data Sources of the VQL Guide). The following update will provide graphical support for this.
The cache engine can now use these databases:
Azure SQL Database
GCP Cloud SQL for MySQL
GCP Cloud SQL for PostgreSQL
Virtual DataPort (ODBC Driver)
Significant performance improvements for queries that return a large number of rows. In some environments, the queries run up to 30% faster. You do not need to update the ODBC driver; the improvement is in the ODBC interface of Virtual DataPort.
Virtual DataPort (Operations and Security)
In the OAuth settings of Virtual DataPort, you can now store a “claim” (i.e. an attribute) of the OAuth token as a “session attribute” of the user. For example, the OAuth tokens of your organization may have a claim with the name of the department of the user. You can configure the OAuth settings to store this claim in the session.
You can also configure the rest of the authentication mechanism to store session attributes (i.e. Kerberos, SAML, LDAP and Denodo Security Token). To do this, open the Server configuration and go the appropriate tab.
For users that log in using LDAP, the “userPrincipalName” is stored in the session.
Then, you can use these session attributes to:
Define a global security policy whose “audience” (i.e. who does it apply to) is the users of this department.
In the initial SQL sentences of JDBC data sources.
Global Security Policies: you can define global security policies that affect users whose “session attribute” meet certain conditions. These conditions can now have the operators IN, LIKE and CONTAINS. Before, the only operator was “=”.
New stored procedure: GET_DATABASES. It returns the name of each database, its description and some of its settings.
Users that have the privilege METADATA over a database (and do not have the privilege WRITE) can now obtain the VQL of the database and its elements. Virtual DataPort will return the VQL but it will not include the “.properties” file, which includes the encrypted values (usernames, passwords…).
You may want to have service accounts dedicated to just do backups. That is, accounts that can export the VQL of a database periodically, and that only need the METADATA privilege. They will be able to obtain the VQL but will not have the usernames/passwords so they cannot run queries nor import the VQL into another Virtual DataPort.
Virtual DataPort - Design Studio
The VQL Shell of Design Studio now has “smart autocomplete” of SELECT queries: when you press Ctrl+Space, the VQL Shell displays a popup with suggestions. These suggestions depend on the position of the cursor within the query. For example, when you type “SELECT * FROM” and press Ctrl+Space, the list shows the views of the database you are connected to. When put the cursor after the “SELECT” and press Ctrl+Space, the list shows the fields of the views in the FROM and much more.
To find and replace: press Ctrl+F or type in the Search box.
When the queries have parsing errors, the VQL Shell highlights where the problem is.
On the top-right side you see the number the number of statements with errors.
With the buttons on the top-right, you can navigate through each error.
The auto-complete feature is for SELECT and CALL statements, not for other commands (CREATE DATASOURCE, CREATE WRAPPER, etc.).
Performance improvements when dealing with requests that have a
$filter nested in a
The Summary tab of views has a new button to display the data of the view in Power BI (it generates a file that creates a data source in Power BI to query the view). The administrator has to enable this option in the Personalization page, in the section External Tools.
When synchronizing the metadata with Virtual DataPort, Data Catalog now imports the tags of Virtual DataPort.
Improvements in the feature of storing the metadata of Scheduler:
Added support for MySQL 8.
It is no longer necessary to manually create the tables in the database, the Scheduler server will create them in the next restart.
Performance improvements in the JDBC exporter: it stores data in Snowflake faster.
Scheduler displays the individual reports of the executions of the parameterized queries successfully executed.
The Automated Cloud Mode now works with the region AWS GovCloud (US).
Added support to store the metadata of Solution Manager in MySQL 8.
Improvements in the management of revisions:
Uses can now delete revisions.
A revision can include Scheduler extensions.
Enhancements that Apply to Several Components
Now, Design Studio, Data Catalog and Scheduler Web Administration Tool can be configured to run behind a reverse proxy (see Proxy Settings (Design Studio, Data Catalog, Scheduler)).
The REST API of Data Catalog and Scheduler now supports OAuth authentication.
Documentation Release Notes
Information about Deprecated Features
The feature of creating ODBC data sources in Virtual DataPort is now deprecated. This feature relies on the JDBC-ODBC bridge of Java. Starting with Java 8, Oracle no longer supports the JDBC-ODBC bridge included in the Java Virtual Machine.
If a database provides a JDBC driver, create a JDBC data source instead of an ODBC one. Queries involving a JDBC data source run faster than if they involve an ODBC data source, even if the underlying database is the same.
Denodo Monitor had a feature that sends SNMP traps with the information received by the Queries monitor or the Cache Monitor. This feature has been removed. If you want to use it, use the Denodo Monitor of 8.0u20220126.
See also: Features Deprecated in Denodo Platform 8.0.