Closed rfk closed 7 years ago
Fwiw, the script is easily tweaked so that it can fill in holes caused by incomplete runs: in the calling script, just set the day_from
argument to import_events.run
to the CSV date you want to start from.
The stack trace here is what happens whenever it thinks there are no unpopulated days, so it will naturally go away when the next CSV is available. But that doesn't mean it will fill in the holes, unless day_from
is explicitly set.
AFAIK these are importing correctly, closing this out
I see this in the mail spool on our redshift helper box:
I recently did a manual import of email events that got killed partway through, which may or may not have put the db in a state that's started causing this to fail.