Skip to content
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

fix: coerce some types from query result set #52

Conversation

ntnhaatj
Copy link

Description

when running dbt source freshness the result could not be coerced to timestamp from response strings

^[[0m06:33:28.268707 [error] [MainThread]: ^[[33mDatabase Error in source bnpl_transaction_get_offers_stag_schema_id_163 (models/bnpl/sources.yml)^[[0m^[[0m06:33:28.268883 [error]
[MainThread]:   Expected a timestamp value when querying field 'ingestion_time' of table bnpl.bnpl_transaction_get_offers_stag_schema_id_163 but received value of type 'str' instead

noticed that from v0.20 dbt-core has been updated to prevent using agate table coercion from SQL adapter query result (dbt-labs/dbt-core#3499)

this PR aims to support the coercion for timestamp type from livy query result set

Checklist

@ntnhaatj ntnhaatj closed this by deleting the head repository Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant