You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using dbt or coalesce we added a Nanosecond to rows in our import-row to achieve uniqueness.
This generates invalid timeframes in the v1-sats because there a Microsecond is subtracted.
Could this be customizable?
Version is 1.1.2
The text was updated successfully, but these errors were encountered:
Next step: New global variable "load_end_date_substraction_unit" with default value "microsecond".
Would have impact on the DATEADD function used in the load_end_date calculation.
This issue is stale because it has been open for 90 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue. Otherwise it will be closed in 14 days
Using dbt or coalesce we added a Nanosecond to rows in our import-row to achieve uniqueness.

This generates invalid timeframes in the v1-sats because there a Microsecond is subtracted.
Could this be customizable?
Version is 1.1.2
The text was updated successfully, but these errors were encountered: