LDW 2.3.1 released: Data Lineage, Row-based Security, Web Business Data Shop, and more
This is the first release of our new 2.3 major release, which includes:
- Column Level Data Lineage
- Row-Based Security and Column Masking
- Web Business Data Shop
- Metadata Visibility Through JDBC/ODBC
Please refer to our blog post regarding a more detailed description of each feature, including screenshots.
Besides the new features, several improvements have been made in comparison to the last 2.1 release. A few highlights:
- Support for Teradata as Analytical Storage
- Support for PostgreSQL 12 as data source
- Zipped upload by default for ingesting data into Redshift for speed improvement
- A new systemd-based script for Linux to manage the Data Virtuality service, replacing the old System V init script
You can find the full changelog below, excluding the new features mentioned in the linked blog post:
DV Web
- DVCORE-6435 (Improvement): Refactoring and redesign
- DVCORE-6496 (Improvement): Add additional SQL samples
Studio
- DVCORE-6767 (New Feature): Add support for Teradata as Analytical Storage
- DVCORE-6695 (Improvement): Add help sections for data source wizards where it is missing
- DVCORE-5435 (Improvement): Add a confirmation message at the end of the export workflow
Connectors
- DVCORE-6811 (Improvement) Redshift: Enable uploadZipped for S3 upload mode by default
- DVCORE-6766 (Improvement): Update the MS SQL JDBC driver to the latest version
- DVCORE-6805 (Improvement): Add support for PostgreSQL 12
- DVCORE-6623 (Improvement): Teradata: Improve the performance of metadata loading
- DVCORE-6807 (Improvement): Make it possible to prevent importing of table and column comments when creating an Oracle data source
- DVCORE-6804 (Improvement): Azure Synapse Analytics: Add the possibility to load data from Blob Storage using Managed Service Identity
- DVCORE-6427 (Improvement): Add support for Oracle INTERVAL data type
- DVCORE-5492 (Improvement): Support automatic refresh of an expired AccessToken for OAuth2
- DVCORE-6801 Teradata: It is impossible to set JDBC properties on creation of connection
- DVCORE-6746 (Improvement): Make it possible to set enableMetadataCache property per data source
Backend
- DVCORE-6830 (Improvement): Create a systemd unit file and integrate it into RPM package
- DVCORE-6829 (Improvement): Remove redundant logging for server started as a service
- DVCORE-6822 (Improvement): Enhance the UTILS.upsert procedure to support BigQuery destinations
- DVCORE-6809 (Improvement): Allow setting max recursion limit to infinity via dv.maxRecursion session property
- DVCORE-4635: NullPointerException when unsuccessfully updating access token using a refresh token
- DVCORE-6748 (Improvement) Data Virtuality Exporter: separate the Data Virtuality JDBC driver into a separate JAR file and make its location configurable
- DVCORE-6803: SELECT COUNT from a UNION of a table and a large CSV file results in "Batch not found in storage" error if combined with GROUP BY
- DVCORE-6756: The maximum length of materialization tables name is too small
Please sign in to leave a comment.
Comments
0 comments