LDWH 2.0.57 released: Negative keywords/support for predicates for Google Ads

After adding the possibility for the Google Ads connector to fetch zero impressions in version 2.0.55, this version adds another feature to the Google Ads connector: Providing predicates, which includes fetching report data for negative keywords.

The Google Ads API specified certain fields to be filterable and formulating the filter condition as a predicate. Here is an example for fetching negative keywords:

SELECT *
FROM (
    EXEC google_ads_src.getAD_PERFORMANCE_REPORT(
        customerId => 123456789,
        startDate => '2017-04-01',
        endDate => '2017-05-01',
        fields => 'Keyword, Date, Conversions, Impressions, Clicks, Ctr, Cost',
        predicates => '[IsNegative,EQUALS,{false}]'
    )
) x ;;

The predicate consists of a field name, operator and value. The Google Ads documentation linked above includes details on what combinations are valid. It is also possible to provide multiple predicates: The expression

[IsNegative,NOT_EQUALS,{true}],[Id,IN,{1,2}]

would filter for negative keywords as well as the keyword ID.

Studio

• DVCORE-5997 (Improvement): Add "More data sources..." item to 'Add data source' wizard

Connectors

• DVCORE-5909 (Improvement) Google Ads: Add a possibility to fetch negative keywords data from Google Ads data source
• DVCORE-6002: Select into with createStringsAsClobs=true and limit 0 fails on MySQL
• DVCORE-4571: Azure SQL Data Warehouse and MS SQL: data type datetimeoffset is mapped to object

Backend

• DVCORE-5869 Improvement Improve lock mechanism of materialized tables for long running jobs
• DVCORE-5999: LDAP Authentication: reading from SYSADMIN.Permissionsis broken
• DVCORE-5926: LEFT JOIN with WHERE returns incorrect results if one of joined sub-queries contains GROUP BY on a UNION ALL of LEFT JOIN
• DVCORE-5031: Creation of connection with incorrect or non-existing properties does not fail but prohibits server from starting