Skip to content

fix: truncate nanosecond-precision timestamps for BigQuery before casting #989

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.

Sign up for GitHub

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

Open
devin-ai-integration wants to merge 1 commit into
base: master
Choose a base branch
from
+16 −0
Open

fix: truncate nanosecond-precision timestamps for BigQuery before casting #989

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions macros/utils/data_types/cast_column.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,22 @@
cast({{ timestamp_field }} as {{ elementary.edr_type_timestamp() }})
{%- endmacro -%}

{#
BigQuery TIMESTAMP only supports microsecond precision (6 fractional digits).
Starting with dbt-bigquery >= 1.11, nanosecond-precision timestamps (9 fractional
digits) may appear in string columns like execute_completed_at. Truncate to
6 fractional digits before casting to avoid "Invalid timestamp" errors.
#}
{%- macro bigquery__edr_cast_as_timestamp(timestamp_field) -%}
cast(
regexp_replace(
cast({{ timestamp_field }} as {{ elementary.edr_type_string() }}),
r'(\.\d{6})\d+',
'\\1'
) as {{ elementary.edr_type_timestamp() }}
)
{%- endmacro -%}

{# Athena and Trino needs explicit conversion for ISO8601 timestamps used in buckets_cte #}
{%- macro athena__edr_cast_as_timestamp(timestamp_field) -%}
coalesce(
Expand Down
Loading