LDWH 2.0.55 released: Configurable connection pool size, zero impressions in Google Ads

When connecting to a data source, Data Virtuality creates a pool of connections to be used by your SQL queries. In previous versions, the size of the connection pool was configurable in a configuration file on the server and defaulted to a minimum of two and a maximum of 70 connections. In version 2.0.55 you can now configure those limits directly in the Studio when creating/editing a data source. Under "Advanced configuration parameters" you can specify the limits as follows:

min-pool-size=3,max-pool-size=7

Data Virtuality would now always keep three connections open and may only use seven connections in total. If your queries require more connections they will be queued by Data Virtuality until another query has finished and released previously used connections.

For customers using the Google Ads connector it is now possible to also include rows with zero impression in the result set of your reports. Zero impression rows will not be returned by default to maintain the prior default behavior, but may be included by setting the parameter includeZeroImpressions to true when calling the connector's procedures.

Studio

• DVCORE-5896: QueryLog viewer allows the start date to be greater than the end date

Connectors

• DVCORE-5866 (Improvement) Google Ads: add a possibility to fetch zero impression data from Google Ads data source
• DVCORE-5949: Google Ads: CpcBid/CpmBid does not allow string values
• DVCORE-5272: Google Ads: invalid data type for ImageCreativeMimeType
• DVCORE-5933: Salesforce: connections are not released after refreshing of the data source and it leads to failures of all further queries
• DVCORE-5034: Hive: replication into or from Hive data source results in "Could not commit transaction" error

Backend

• DVCORE-5661 (Improvement): Make it possible to set connection pool size on creation of data source
• DVCORE-5960 (Improvement): Improve UTILS.tryCast by introducing pre-defined date/timestamp parsing formats
• DVCORE-5918: Replications fail if column name contains a space
• DVCORE-5819: Alias is not removed from the referenced column in UTILS.getTableIntersection
• DVCORE-5487: Passing NULL as a value to XMLTABLE results in an error
• DVCORE-5301: TIMESTAMPCREATE in SELECT combined with GROUP BY clause results in ORDER BY working incorrectly
• DVCORE-5196: EvalName function throws an error, when applied to a data source
• DVCORE-5151: Upsert job: no validation is done for the surrogate key type