Update data_freshness_assertions.js

[alexvys]

This resolves the error of when you are trying to use HOURS instead of just using days/weeks/months/etc.

[alexvys]

Hi @hrialan

I've checked it in my environment and this resolved the issue of using 'hour' and other timestamp fields in the freshness checks. Without this implementation any assertion for a timestamp field (like checks for the freshness of <4h would result in an error like this "Query error: DATE_DIFF does not support the HOUR date part when the argument is DATE type at [18:25]".

Please approve the pull request :)

[alexvys]

Hey @hrialan :)
Could you please approve this tiny pull request? This would help me a lot! Thank you!

[hrialan]

@alexvys it seems not to work, I will revert changes

[alexvys]

Hmm... That's weird... maybe because the timezone was added in between the versions that I was using

Here is what worked for me.

[alexvys]

Maybe this is the solution then:

TIMESTAMP_DIFF(CURRENT_TIMESTAMP("${timeZone}"), MAX(${dateColumn}), ${timeUnit}) AS delay