-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] dbt source freshness expected a timestamp but received a string #631
Comments
Leaving this for anyone picking this up. Alternatively, but a bit more complicated, on the python side, we can overwrite this method in the adapter:
|
From my side I can add than I propose override select
max(<ts_column>) as max_loaded_at,
{{ current_timestamp() }} as snapshotted_at
from <source_table> For partitioned Iceberg tables use the following query: select
max(data.<partitioned_by_ts_column>.max) as max_loaded_at
from "<source_schema>"."<source_table>$partitions" |
Is this a new bug in dbt-athena?
Current Behavior
I'm trying to run a freshness check on some of my tables using a timestamp column. However, I'm getting an error saying the check found a str column instead of a timestamp one. I believe this is a bug, because athena shows my column as a timestamp according to the following image.
The error I'm getting is also in the following image:
My dbt_athena package in in version 1.7.2. The query generated by the freshness code is below as the results it produced
Expected Behavior
The dbt source freshness command should be able to run successfully on my source tables. Otherwise, it should point some error related with the SLA configured, not throw an error related with casting types.
Steps To Reproduce
version: 2
run the command
dbt source freshness
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: