Fixed issue with upgrading metadata table in AWS Redshift #1231 #1256
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…failed Flyway couldn't upgrade the metadata table, due to the following error: "Amazon Invalid operation: cannot insert/update into table after dropping non-nullable column" This was caused by trying to remove the NOT NULL constraint on the version column by adding/dropping a temp columan and copying the values. For somae unknown reason, this works on some versions of Redshift, but not others. The solution is just to rename the original table, create a new one, copy the data, and drop the original table.
Redshift does not support indexes because it is a column-oriented database. Instead data can be physically stored sorted, to improve reading and sorting performance, based on the sort key.
….2.1 to 4.0 failed When renaming a table, the schema should not be specified in the new table name.
|
Thanks Nathan! Merged. |
|
@nathanvick Could you please contact me by email at axel at boxfuse dot com ? Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes the issue where upgrading the metadata table (from Flyway v3.2.1 to v4.0) failed, for at least some installations of AWS Redshift. Redshift does not support altering columns within a table. There are two common workarounds for this:
This pull request changes the approach from "copying data between temp columns" to "copying data between temp tables" because the former approach requires a commit half way through the process, for some installations of Redshift.