Closed johnoscott closed 3 months ago
Hi, it's an epoch timestamp.
See https://www.epochconverter.com/ For snowflake, use https://docs.snowflake.com/en/sql-reference/functions/to_timestamp
Not possible to cast as timestamp. This is due to sling dealing with many systems, epoch is a timezone neutral, universal value. You could maybe use post_sql
to update the target table? Or create a view.
All right, thinking of it, I've reconsidered and will add logic to accept SLING_LOADED_AT_COLUMN='timestamp'
so the column will be casted as native timestamp. SLING_LOADED_AT_COLUMN='true'
will still use default epoch / unix timestamp.
Yes its more of a convenience feature, so I appreciate you agreeing to make the change.
Added with https://github.com/slingdata-io/sling-cli/pull/318/commits/f53d09246b5ac00a3cd0ef7165a2ef02437eacb1 for next release. Closing.
Issue Description
The docs describe the
_SLING_LOADED_AT
column as a timestamp, but it is created in Snowflake as a NUMBER(38,0) type.Is it possible to specify the type so i can avoid having to cast it :
I have tried specifying a column type but it doesnt work :
sling --version
):Version: 1.2.11
linux
,mac
,windows
):mac
see above
-d
):