Rolling back adding retention instructions to sample table #657
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #633
Changes proposed in this pull request
retention_instruction
column insample
table.This migration has already been applied in UAT warehouse. We can introduce a
remove_column
migration but that will cause problems when the two migrationsadd_column
andremove_column
goes into production asadd_column
insample
table is a huge task (as it is ~4Gi in size).So the suggested change rollbacks the changes done for adding retention instructions to
sample
table, so that it will have no effect on thesample
table in production. The migration added to UAT database is to be manually removed.Instructions for Reviewers
[All PRs] - Confirm PR template filled
[Feature Branches] - Review code
[Production Merges to
main
]- Check story numbers included
- Check for debug code
- Check version