-
Notifications
You must be signed in to change notification settings - Fork 2
Updated with common schema files and seperated postgres data migration #425
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
Open
chenchals
wants to merge
7
commits into
main
Choose a base branch
from
chenchals/DT-409-Aou-Tanagra-common-schema-files
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
460d426
Updated with common schema files and seperated postgres data migration
chenchals 6d12c40
set export TANAGRA_DB_INITIALIZE_ON_START=true
chenchals 07eace6
Updated with common schema files and seperated postgres data migration
chenchals f8613d3
set export TANAGRA_DB_INITIALIZE_ON_START=true
chenchals fa1775c
Updated to use column names property_key, property_value, criteria_ke…
chenchals bc4b30e
Merge remote-tracking branch 'origin/chenchals/DT-409-Aou-Tanagra-com…
chenchals f950f3d
Changed TANAGRA_DB_INITIALIZE_ON_START=false as appropriate for main …
chenchals File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
22 changes: 22 additions & 0 deletions
22
service/src/main/resources/db/changesets/20230602_postgres_data_migrate.yaml
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| databaseChangeLog: | ||
| - changeSet: | ||
| id: postgres_data_migrate | ||
| author: marikomedlock, chenchalsubraveti | ||
| dbms: postgresql | ||
| # TODO: Remove the jsonb and 2 text[] columns in a follow-on changeset, once we're sure this migration was successful. | ||
| # study.properties, criteria.tags, annotation_key.enumVals | ||
| changes: | ||
| - sql: | ||
| # Migrate the properties of existing studies from the JSON column to this table. | ||
| sql: | | ||
| INSERT INTO study_property (study_id, property_key, property_value) | ||
| SELECT id, key, properties->>key as value | ||
| FROM (SELECT id, jsonb_object_keys(properties) as key, properties FROM study) AS study_property_keys; | ||
|
|
||
| # No migration SQL because the criteria.tags text[] column is not yet being used by the UI. | ||
|
|
||
| - sql: | ||
| # Migrate the enum values of existing annotation keys from the text[] column to this table. | ||
| sql: | | ||
| INSERT INTO annotation_key_enum_value (cohort_id, annotation_key_id, enum) | ||
| SELECT cohort_id, id AS annotation_key_id, unnest(enum_vals) AS enum FROM annotation_key; |
This file contains hidden or 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
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.
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.
This changeset file has already been deployed to our test instance (we deploy nightly), so you can't change the name or any of the schema specification for postgres. If you change it to render differently for mariadb/mysql only, then I think that's okay (though I'd want to test to confirm) but changing the postgres rendering will definitely break things.
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 do not follow.