[X] I believe this is a new bug in dbt-expectations
[x] I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
Using the expect_table_aggregation_to_equal_other_table test on a DATETIME, TIMESTAMP or DATE column returns the following error. I think this might be specific to BigQuery, because its COALESCE() function doesn't accept different data types and there's an integer literal amidst the test implementation.
Expected Behavior
expect_table_aggregation_to_equal_other_table would compare two different DATETIME types and return PASS if they're the same.
Database Error in test Database Error in test dbt_expectations_expect_table_aggregation_to_equal_other_table_ods_contacts_max_UpdatedDate___source_intercom_legacy_contacts___max_updated_date_ (models/intercom/__intercom.yml)
No matching signature for function COALESCE for argument types: DATETIME, INT64. Supported signature: COALESCE([ANY, ...])
A workaround to fellows out there who are eager to use this feature, use safe_cast and unix_millis to convert dates, datetimes or timestamp to integers and work from there
Is this a new bug in dbt-expectations?
Current Behavior
Using the expect_table_aggregation_to_equal_other_table test on a DATETIME, TIMESTAMP or DATE column returns the following error. I think this might be specific to BigQuery, because its COALESCE() function doesn't accept different data types and there's an integer literal amidst the test implementation.
Expected Behavior
expect_table_aggregation_to_equal_other_table would compare two different DATETIME types and return PASS if they're the same.
Steps To Reproduce
Setup .yml file as follows:
Relevant log output
Environment
Which database adapter are you using with dbt?
BigQuery 1.7.7
Note: dbt-expectations currently does not support database adapters other than the ones listed below.
Additional Context