-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replicate foorm tables to Redshift #35374
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’m still investigating the failures exporting to Redshift that occurred the last 2 days, so check with my before applying this stack update.
I'm ready to make it @sureshc, can you just comment here when it's ok to do so? |
Will do |
@bencodeorg Looks like this recent change to the size of the levels.properties column is causing the export to Resdhift to fail. Unlikely we’ll have a resolution today. |
@bencodeorg I’m still investigating the export error that occurred Mon & Tue. The Wednesday export mysteriously succeeded, so it’s fine for you to apply this change while I continue to investigate the issue with the levels table. |
Success -- checked in AWS web console that
|
Replicates
foorm
tables to Redshift. There might befoorm_
tables that don't contain PII, but following precedent withpd_
tables where we put everything indashboard_production_pii
schema. I think this is a good pattern so that everything in a given namespace appears in the same schema, instead of being split across the two (dashboard_production
anddashboard_production_pii
).Testing story
So far, just checked whether this looks like it would appropriately update the cron-pii DMS task:
Once approved, can run
RAILS_ENV=production bundle exec rake stack:data:start
to actually modify the CloudFormation template.