fix: coerce some types from query result set #52
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
when running
dbt source freshness
the result could not be coerced to timestamp from response stringsnoticed 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
changie new
to create a changelog entry