Open alexanderdean opened 7 years ago
See https://snowplow.zendesk.com/agent/tickets/5238 for latest context
This ticket assumes that we want to put bigint limits on the schema and bump the Redshift type to bigint too. Not sure if this makes total sense given this is meant to represent a timing - how big can an elapsed duration be? /cc @chuwy and @BenFradet
Another related issue: https://github.com/snowplow/iglu-central/issues/382
Is this schema supposed to be used only by JavaScript tracker? If so then maximum duration with INTEGER
is 24 days (2147483647 / 1000 / 3600 / 24) looks more than enough for web page. Having that I think we should fix JSON Schema, not Redshift table.
Closing in favour of #382.
Reopening, sorry for confusion.
Make the
timing
column aBIGINT
, not anINT
.Migrated to https://github.com/snowplow/snowplow/issues/2818