LDW 2.3.4 released: Various improvements

This release includes various improvements, such as better error messages, more sensible default values for Oracle connections and a fix for the Google Analytics v4 API.

Web

• DVCORE-6866: NullPointerException when querying datetime data types with NULL values

Studio

• DVCORE-6815 (Improvement): Rename Azure SQL Data Warehouse into Azure Synapse Analytics
• DVCORE-6405 (Improvement): Set default values of importer.schemaPattern and importer.defaultSchema properties for the Oracle data source equal to the user name
• DVCORE-5542 (Improvement): Improve usability of users and roles management
• DVCORE-5016: The error dialogue info message gets truncated

Connectors

• DVCORE-6858: Oracle: Some columns are skipped during the metadata fetching on Oracle data source creation
• DVCORE-6836: Google Analytics: Segments do not work via getV4 procedure
• DVCORE-6832: Google Ads: An 'invalid long format in string' error when running getSEARCH_QUERY_PERFORMANCE_REPORT with a certain set of parameters
• DVCORE-6784: Teradata: Indexes are not supported
• SQL-215: Pardot: Rename credentials to store in the connection properties

Backend

• DVCORE-6796 (Improvement): Enable the XML parser to distinguish between empty and spaces-only values
• DVCORE-6788 (Improvement): Improve the error message for trying to connect to data sources with missing JDBC drivers
• DVCORE-6456 (Improvement): Validate connection properties and throw an error if an invalid property is attempted
• DVCORE-6857: Common Table Expressions: INNER JOINs of two CTEs fail with an ASSERTION FAILED error
• DVCORE-6715: Materialization of UTF8 characters fails for Microsoft SQL Server and Oracle Analytical Storage