colmsnowplow

Results 44 comments of colmsnowplow

@crosbygw I notice you're also on arm - I resolved by setting `export TFENV_ARCH=amd64`. Works as expected for me once that's set!

The most recent commits, following from a meeting to discuss design after seeing example failure data: - Define failureType as the classification of the failure, rather than anything to do...

I like the plan! > One potential problem might be if the backfill is particularly large it may not be possible to process all data in one go. In which...

That could be a nice solution! I think there's likely some some clever configuration solution to resolve the referencing issue. What I really like about this idea is that it...

Good catch @emielver. It may well be the case that in v1 the upper limit was included for some eventuality that I thought would matter, but in reality doesn't. If...

It's min_tstamp in Redshift too https://github.com/snowplow/data-models/blob/e1e10fb696a52aa9bc990e975154405779f421de/web/v1/redshift/sql-runner/sql/standard/03-sessions/01-main/05-sessions-prep-manifest.sql#L27 I'm on board with changing the name to whatever. I think I went with min_tstamp as it represents the first timestamp found for a...

> This looks like a copy paste error - please delete. Not a copy paste error. The stored procedures are used in each module, the step that creates them needs...

ZD ticket reference 26783 for an example (closed source) of when this comes into focus

Fair point @alexanderdean - we ended up here because we hadn't had docs written yet when the readmes were created. We used the readmes as basis for docs. If I'm...