Data Virtuality Platform 4.0.2: an important improvement, two new connectors, and many bug fixes

This release has an improvement for the Server, two new connectors, and a number of bug fixes for different components of the Data Virtuality Platform.

Most importantly, we've released a new Data Virtuality Auth Management component: you can now use a third-party identity provider, such as Azure AD, for authentication in the Data Virtuality Platform. If you want to try it, please contact our support team (and we'll be happy to hear your feedback!).

In other news, the Server now has a special stored procedure for cleaning the ResultSet cache - it is called SYSADMIN.clearResultSetCache().

As for bug fixes, most importantly, we've resolved the issue with "AssertionError: Batch not found in storage" thrown by the replication jobs when local temporary tables are used, and the issue causing LEFT JOIN of system tables related to modular connectors to yield incorrect result due to incorrect primary keys set. Now all is well.

We've also fixed two bugs affecting OAuth2: one that the Keycloak user "admin" with no role assigned on the Keycloak server could connect to the Data Virtuality Server and access any data sources, and another causing the session to expire and the Studio to shuts down. Now everything works securely and properly.

The CREATE OR REPLACE query with option $NOFAIL now also works properly in three cases where there were problems previously: in SQL jobs, when used in procedures, and in BEGIN END block.

Last but not least, the SYSADMIN.writeConnProp procedure now validates the property name as it should, and the "connect-dv-role" now has all permissions needed for the new web UI.

On the Studio side, we've fixed the bug which caused editing views and procedures to fail with a "No match available" error, and for the Exporter, we've resolved the issue with using OAuth2 or OpenID with CLI Exporter: username and password won't be required if one of these types of authentication is used.

Finally, we're happy to present two new connectors: Bol and ManoMano. We've also fixed a bug affecting the Exasol connector: previously, casting of DOUBLE to VARCHAR caused zero after the decimal point to disappear, and now everything works properly. 

Here are all issues in this release:

Server

• DVCORE-7955 (Improvement): Implement a stored procedure for cleaning the ResultSet cache
• DVCORE-7978 (Bug Fix): "AssertionError: Batch not found in storage" is thrown by the replication jobs when local temporary tables are used
• DVCORE-7972 (Bug Fix): OAuth2: Keycloak user "admin" with no role assigned on the Keycloak server can connect to the Data Virtuality Server and access any data sources
• DVCORE-7971 (Bug Fix): OAuth2: session expires and Studio shuts down, even if some actions are performed in it
• DVCORE-7970 (Bug Fix): CREATE OR REPLACE query with option $NOFAIL fails when used in SQL job
• DVCORE-7967 (Bug Fix): CREATE OR REPLACE query with option $NOFAIL fails when used in procedures
• DVCORE-7966 (Bug Fix): CREATE OR REPLACE query with $NOFAIL option fails in BEGIN END block
• DVCORE-7933 (Bug Fix): LEFT JOIN of system tables related to modular connectors yields incorrect result due to incorrect primary keys set
• DVCORE-7927 (Bug Fix): SYSADMIN.writeConnProp procedure does not validate the property name
• DVCORE-7921 (Bug Fix): The "connect-dv-role" lacks some permissions required by the new web UI

Studio

• DVCORE-7973 (Bug Fix): edit view and edit procedure fails with "No match available" error

Exporter

• DVCORE-7976 (Bug Fix): username and password are required parameters if OAuth2 or OpenID authentication is used with CLI Exporter

Connectors

• SQL-615 (New Feature): Bol: create connector
• SQL-477 (New Feature): ManoMano: create a connector
• DVCORE-7876 (Bug Fix): Exasol: casting of DOUBLE to VARCHAR causes zero after the decimal point to disappear